[feat] detect if app tries to access query with prerender enabled#2104
Conversation
🦋 Changeset detectedLatest commit: bda1b98 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
ebdd3ac to
956a2d9
Compare
956a2d9 to
bda1b98
Compare
|
Sorry, why prevent them from accessing query while prerendering? You could have fixed options for query string in the pages array, like: i.e. nonparameterized query string options. This change breaks that pattern right? |
|
Also, do you guys not require another pair of eyes to review each change going in? |
I don't think you could even before this change. But I'm not sure whether it is something we should support. E.g. what would happen if someone requests We ask for reviews on things that are a bit larger such as changes in APIs, etc. This PR was open for almost a week, so the community could comment on it and the proposed plan was mentioned months ago in the associated issue, so didn't rise to that level |
|
Got it. Ah yes, I totally forgot about my #1825, query strings don't even work at the moment anyway. This actually makes it so they probably won't ever, which is of course fine for new websites. The only issue might be if you're porting an existing website to SvelteKit and want to match the URL form precisely, it could be a problem. Maybe any discussion can continue in #1825. |
Closes #669