Skip to content
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

[vue] Add error handling toast #16505

Merged
merged 3 commits into from
Oct 2, 2021
Merged

Conversation

swarajsaaj
Copy link
Contributor

Add error handling for multiple scenarios in Vue with a toast.

Approach:- The errors are being shown in the toast through a service instead of interceptor to allow users more choice over generated code to pick and choose errors they wish to show/handle.

Fix #16393


Please make sure the below checklist is followed for Pull Requests.

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

Add error handling for multiple scenarios in Vue with a toast.

Fix jhipster#16393
@@ -0,0 +1,61 @@
import Vue from 'vue';

export default class AlertService {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it possible to have alert.service.spec.ts too plz ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added for translation/entity-header scenarios in 02c6214 :)

@pascalgrimaud pascalgrimaud merged commit de416a2 into jhipster:main Oct 2, 2021
@swarajsaaj
Copy link
Contributor Author

Thanks for review and merge @pascalgrimaud

@swarajsaaj
Copy link
Contributor Author

@pascalgrimaud
Copy link
Member

@swarajsaaj : approved !

@pascalgrimaud pascalgrimaud added this to the 7.3.0 milestone Oct 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When there is a backend error, no error message shows up in the front end.
2 participants