-
Notifications
You must be signed in to change notification settings - Fork 10
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
Apex exceptions raised to local server LWC components display incorrect error messages #101
Labels
Comments
This issue has been automatically marked as |
This issue has been linked to a new work item: W-8868333 |
This issue has been automatically marked as |
Error while creating work item. No valid build found in GUS! |
This issue has been automatically marked as |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When an exception is raised from Apex, and the LWC is being served from the LWC local dev server, there is a difference in treating that exception such that you need different code to properly surface the error in the UI. This was discovered when investigating a PR in the LWC Recipes sample app.
To Reproduce
Steps to reproduce the behavior:
Run that component in local lwc server. The error is surfaced in one way.
Deploy component to an org. In that instance, the error surfaced contains the message intended from Apex.
Expected behavior
The shape of the object returned by an error should be identical between LWC when hosted in an org, and when it is hosted in the local server.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: