-
Notifications
You must be signed in to change notification settings - Fork 75
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
Unify success alerts #1469
Unify success alerts #1469
Conversation
68a1946
to
b39e900
Compare
499bdd0
to
f12761b
Compare
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.
In global looks good, but I have concerns regarding to the translation. See the comments bellow.
src/containers/certification-dashboard/certification-dashboard.tsx
Outdated
Show resolved
Hide resolved
src/containers/execution-environment-list/execution_environment_list.tsx
Outdated
Show resolved
Hide resolved
22a8956
to
f53783d
Compare
src/components/delete-modal/delete-execution-environment-modal.tsx
Outdated
Show resolved
Hide resolved
src/containers/certification-dashboard/certification-dashboard.tsx
Outdated
Show resolved
Hide resolved
src/containers/execution-environment-detail/execution_environment_detail_images.tsx
Outdated
Show resolved
Hide resolved
@ShaiahWren you may have missed some ... (Are you splitting the effort in multiple PRs or should I try checking for more missing success messages?) |
64e6048
to
dcfb4d4
Compare
@himdel AlertType now accepts JSXElement or string for the title, however, as you can see the bold doesn't seem to be showing up in the alerts. Is it my syntax? I will continue to work on the other items. Thank you for the thorough review. :) |
dcfb4d4
to
13ef838
Compare
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
Issue: AAH-1236
5834e5b
to
47ab4f1
Compare
noticed in ansible#1738, looks like this was introduced in ansible#1469 to replace "Successfully deleted collection." we're now using the same success message in `deleteCollection` and `deleteCollectionVersion`, which is misleading (they didn't just delete one version), and broken since there is no version info, just the `v` updating to remove the version info
noticed in ansible#1738, looks like this was introduced in ansible#1469 to replace "Successfully deleted collection." we're now using the same success message in `deleteCollection` and `deleteCollectionVersion`, which is misleading (they didn't just delete one version), and broken since there is no version info, just the `v` updating to remove the version info No-Issue
noticed in ansible#1738, looks like this was introduced in ansible#1469 to replace "Successfully deleted collection." we're now using the same success message in `deleteCollection` and `deleteCollectionVersion`, which is misleading (they didn't just delete one version), and broken since there is no version info, just the `v` updating to remove the version info No-Issue
* deleteCollection - don't mention version when deleting the whole noticed in #1738, looks like this was introduced in #1469 to replace "Successfully deleted collection." we're now using the same success message in `deleteCollection` and `deleteCollectionVersion`, which is misleading (they didn't just delete one version), and broken since there is no version info, just the `v` updating to remove the version info No-Issue * collection.js test - fix expected alert message to match
See issue: https://issues.redhat.com/browse/AAH-1236
Assignment: Update success alerts to fit modular format outlined in the documentation. Also see additional documentation for general messages.
This pr updates all alerts messages across the application according to the above documentation. In some cases, missing alerts were added.