-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rename App.PageError
to App.Error
#6963
Conversation
🦋 Changeset detectedLatest commit: 2f0f71e The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
Do you want to implement the "try to rename that inside |
I agree with Dominik that it's probably a slippery slope. I think throwing an error telling the user to change it could be good, it just felt like a lot of effort when considering that we don't enforce a specific location for the user to declare those namespaces |
We don't but I guess that 90% of the 5% of people that use this have it inside |
Not sure if it matters much, but even if PageError is commented in app.d.ts/js, the error will be produced: // app.d.ts
// interface PageError {} |
Mhm yeah that's probably very annoying for everyone who doesn't even use it - probably worth expanding the check to see if it's commented out. |
closes #6905. This is a breaking change, but I expect it to be very limited in impact.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. All changesets should bepatch
until SvelteKit 1.0