-
Notifications
You must be signed in to change notification settings - Fork 32
🎨 [Frontend] Wording: Don't say Failed, say Unsuccessful #7361
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
Merged
Merged
Changes from 13 commits
Commits
Show all changes
35 commits
Select commit
Hold shift + click to select a range
161e46c
"Failed" -> "Unsuccessful"
odeimaiz 58a7959
Failed -> Unsuccessful
odeimaiz 5950f65
@pcrespov messages-guidelines.md
odeimaiz 7fd3fb3
minor
odeimaiz 8b27500
Unsuccessful Login
odeimaiz 566187d
a lot of replacing
odeimaiz 755019e
pass error to logError
odeimaiz 29a5e1b
Merge branch 'master' into dont-say-fail
odeimaiz 577e60d
move console.error
odeimaiz 94d1a8f
getMessage
odeimaiz 6186177
oopsi
odeimaiz 87a94fb
extractMessage
odeimaiz 87f9c4e
Merge branch 'master' into dont-say-fail
odeimaiz df7a040
minors
odeimaiz 4a95aaf
Merge branch 'dont-say-fail' of github.com:odeimaiz/osparc-simcore in…
odeimaiz 091ad0a
Update services/static-webserver/client/source/class/osparc/auth/ui/L…
odeimaiz 384a0c8
Update services/static-webserver/client/source/class/osparc/file/File…
odeimaiz 96ed2e5
Update services/static-webserver/client/source/class/osparc/desktop/p…
odeimaiz 5511b20
Update services/static-webserver/client/source/class/osparc/file/File…
odeimaiz 3717274
Update services/static-webserver/client/source/class/osparc/info/Merg…
odeimaiz a39947c
Update services/static-webserver/client/source/class/osparc/study/Stu…
odeimaiz 2964ed0
Update services/static-webserver/client/source/class/osparc/info/Serv…
odeimaiz e308e39
Update services/static-webserver/client/source/class/osparc/info/Stud…
odeimaiz 0b2af5f
Update services/static-webserver/client/source/class/osparc/desktop/o…
odeimaiz c93f0f7
Something went wrong while
odeimaiz 1afd64c
There was an error
odeimaiz 742c9b7
update startupCalls test
odeimaiz e38e7d3
minor
odeimaiz cb288df
remove waitForNetworkIdle
odeimaiz cf94293
Update startupCalls.test.js
odeimaiz 5998844
Update startupCalls.test.js
odeimaiz bc24d09
Merge branch 'master' into dont-say-fail
odeimaiz 4758d16
maxWorkers
odeimaiz e2ca9a7
maxWorkers
odeimaiz ab1a307
maxConcurrency
odeimaiz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,134 @@ | ||
| # Error and Warning Message Guidelines | ||
|
|
||
| These guidelines ensure that messages are user-friendly, clear, and helpful while maintaining a professional tone. 🚀 | ||
|
|
||
| Some details: | ||
|
|
||
| - Originated from [guidelines](https://wiki.speag.com/projects/SuperMash/wiki/Concepts/GUI) by @eofli and refined iterating with AI | ||
| - Here’s the fully expanded and rewritten list of **error and warning message guidelines**, each with: | ||
| - A **guideline** | ||
| - A **rationale** | ||
| - A ❌ **bad example** | ||
| - A ✅ **good example** | ||
| - A **reference** | ||
| - This list is intended to be short enough to be read and understood for humans as well as complete so that it can be used as context for automatic correction of error/warning messages | ||
|
|
||
| --- | ||
|
|
||
| ## 1. Be Clear and Concise | ||
|
|
||
| - **Guideline:** Use straightforward language to describe the issue without unnecessary words. | ||
| - **Rationale:** Users can quickly understand the problem and take corrective action when messages are simple and to the point. | ||
| - ❌ **Bad Example:** | ||
| `"An error has occurred due to an unexpected input that couldn't be parsed correctly."` | ||
| - ✅ **Good Example:** | ||
| `"We couldn't process your request. Please check your input and try again."` | ||
| - **[Reference](https://uxwritinghub.com/error-message-examples/)** | ||
|
|
||
| --- | ||
|
|
||
| ## 2. Provide Specific and Actionable Information | ||
|
|
||
| - **Guideline:** Clearly state what went wrong and how the user can fix it. | ||
| - **Rationale:** Specific guidance helps users resolve issues efficiently, reducing frustration. | ||
| - ❌ **Bad Example:** | ||
| `"Something went wrong."` | ||
| - ✅ **Good Example:** | ||
| `"Your session has expired. Please log in again to continue."` | ||
| - **[Reference](https://www.nngroup.com/articles/error-message-guidelines/)** | ||
|
|
||
| --- | ||
|
|
||
| ## 3. Avoid Technical Jargon | ||
|
|
||
| - **Guideline:** Use plain language instead of technical terms or codes. | ||
| - **Rationale:** Non-technical users may not understand complex terminology, hindering their ability to resolve the issue. | ||
| - ❌ **Bad Example:** | ||
| `"Error 429: Too many requests per second."` | ||
| - ✅ **Good Example:** | ||
| `"You’ve made too many requests. Please wait a moment and try again."` | ||
| - **[Reference](https://cxl.com/blog/error-messages/)** | ||
|
|
||
| --- | ||
|
|
||
| ## 4. Use a Polite and Non-Blaming Tone | ||
|
|
||
| - **Guideline:** Frame messages in a way that doesn't place blame on the user. | ||
| - **Rationale:** A respectful tone maintains a positive user experience and encourages users to continue using the application. | ||
| - ❌ **Bad Example:** | ||
| `"You entered the wrong password."` | ||
| - ✅ **Good Example:** | ||
| `"The password doesn't match. Please try again."` | ||
| - **[Reference](https://atlassian.design/content/writing-guidelines/writing-error-messages/)** | ||
|
|
||
| --- | ||
|
|
||
| ## 5. Avoid Negative Words and Phrases | ||
|
|
||
| - **Guideline:** Steer clear of words like "error," "failed," "invalid," or "illegal." | ||
| - **Rationale:** Positive language reduces user anxiety and creates a more supportive experience. | ||
| - ❌ **Bad Example:** | ||
| `"Invalid email address."` | ||
| - ✅ **Good Example:** | ||
| `"The email address format doesn't look correct. Please check and try again."` | ||
| - **[Reference](https://atlassian.design/content/writing-guidelines/writing-error-messages/)** | ||
|
|
||
| --- | ||
|
|
||
| ## 6. Place Messages Appropriately | ||
|
|
||
| - **Guideline:** Display error messages near the relevant input field or in a clear, noticeable location. | ||
| - **Rationale:** Proper placement ensures users notice the message and understand where the issue occurred. | ||
| - ❌ **Bad Example:** | ||
| Showing a generic "Form submission failed" message at the top of the page. | ||
| - ✅ **Good Example:** | ||
| Placing "Please enter a valid phone number" directly below the phone input field. | ||
| - **[Reference](https://www.smashingmagazine.com/2022/08/error-messages-ux-design/)** | ||
|
|
||
| --- | ||
|
|
||
| ## 7. Use Inline Validation When Possible | ||
|
|
||
| - **Guideline:** Provide real-time feedback as users interact with input fields. | ||
| - **Rationale:** Inline validation allows users to correct errors immediately, enhancing the flow and efficiency of the interaction. | ||
| - ❌ **Bad Example:** | ||
| Waiting until form submission to show all validation errors. | ||
| - ✅ **Good Example:** | ||
| Displaying "Password must be at least 8 characters" while the user types. | ||
| - **[Reference](https://cxl.com/blog/error-messages/)** | ||
|
|
||
| --- | ||
|
|
||
| ## 8. Avoid Using All-Caps and Excessive Punctuation | ||
|
|
||
| - **Guideline:** Refrain from writing messages in all capital letters or using multiple exclamation marks. | ||
| - **Rationale:** All-caps and excessive punctuation can be perceived as shouting, which may frustrate users. | ||
| - ❌ **Bad Example:** | ||
| `"INVALID INPUT!!!"` | ||
| - ✅ **Good Example:** | ||
| `"This input doesn't look correct. Please check and try again."` | ||
| - **[Reference](https://uxwritinghub.com/error-message-examples/)** | ||
|
|
||
| --- | ||
|
|
||
| ## 9. Use Humor Sparingly | ||
|
|
||
| - **Guideline:** Incorporate light-hearted language only when appropriate and aligned with the application's tone. | ||
| - **Rationale:** While humor can ease tension, it may not be suitable for all users or situations and can sometimes be misinterpreted. | ||
| - ❌ **Bad Example:** | ||
| `"Oopsie daisy! You broke something!"` | ||
| - ✅ **Good Example:** | ||
| `"Something went wrong. Try again, or contact support if the issue continues."` | ||
| - **[Reference](https://cxl.com/blog/error-messages/)** | ||
|
|
||
| --- | ||
|
|
||
| ## 10. Offer Alternative Solutions or Support | ||
|
|
||
| - **Guideline:** If the user cannot resolve the issue independently, provide a way to contact support or access help resources. | ||
| - **Rationale:** Offering support options ensures users don't feel stranded and can seek help to resolve their issues. | ||
| - ❌ **Bad Example:** | ||
| `"Access denied."` | ||
| - ✅ **Good Example:** | ||
| `"You don't have permission to view this page. Contact support if you think this is a mistake."` | ||
| - **[Reference](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-error-handling-guidelines/)** |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.