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

Errors are not shown in the UI #10

Closed
Potherca opened this issue Jun 16, 2023 · 1 comment · Fixed by #57
Closed

Errors are not shown in the UI #10

Potherca opened this issue Jun 16, 2023 · 1 comment · Fixed by #57
Labels
enhancement New feature or request

Comments

@Potherca
Copy link
Member

When an API call is done and an error occurs, no error reporting is done.

This was discovered when debugging #9. Even if the response triggers a 500 error response, the client-side code does not report the error happening.

@Potherca Potherca added the enhancement New feature or request label Jun 16, 2023
@Potherca
Copy link
Member Author

The easiest reproduction scenario is to create a component, add a HTML template, fill in some HTML but not a name.

This will trigger an Uncaught Error "Required part name is empty" (in simplycode line 679).

@Potherca Potherca pinned this issue Jun 28, 2024
@ylebre ylebre closed this as completed in #57 Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant