-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
docs: rework docs around errors #11802
Conversation
|
- Contextual information may be used to enhance the message or the hint. However, the code that caused the error or the position of the error should not be included in the message as they will already be shown as part of the error. | ||
- Do not prefix `title`, `message` and `hint` with descriptive words such as "Error:" or "Hint:" as it may lead to duplicated labels in the UI / CLI. | ||
- Dynamic error messages must use the following shape: | ||
- Dynamic error messages **must** use the following shape: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
next step will be in all caps (or writing an ESLint plugin)
How would docs rework this part? |
I'm not sure I understand what you mean? |
Co-authored-by: Chris Swithinbank <[email protected]>
When we remove an error that was previously published, are we going to send the users to an URL that is 404? |
No, see the linked docs PR |
Thank you! |
Changes
People keep removing errors, we cannot change people, but we can make it acceptable to remove errors if that's what more intuitive.
I also took this opportunity to refine some parts of the document
Testing
N/A
Docs
It's all docs