-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Templating exporter should have clear error reporting #3382
Copy link
Copy link
Closed
Labels
Module: FrontendThese issues involve working on HTML, CSS, and JavaScript code that affects the user interface.These issues involve working on HTML, CSS, and JavaScript code that affects the user interface.Type: Feature RequestIdentifies requests for new features or enhancements. These involve proposing new improvements.Identifies requests for new features or enhancements. These involve proposing new improvements.error handlingImproving the ways errors are reported to usersImproving the ways errors are reported to usersexport: templateAbout the custom templating exporterAbout the custom templating exporter
Milestone
Metadata
Metadata
Assignees
Labels
Module: FrontendThese issues involve working on HTML, CSS, and JavaScript code that affects the user interface.These issues involve working on HTML, CSS, and JavaScript code that affects the user interface.Type: Feature RequestIdentifies requests for new features or enhancements. These involve proposing new improvements.Identifies requests for new features or enhancements. These involve proposing new improvements.error handlingImproving the ways errors are reported to usersImproving the ways errors are reported to usersexport: templateAbout the custom templating exporterAbout the custom templating exporter
Currently when your code in the Templating exporter has a problem, the Preview window will just show "Updating..." forever.
It would be good to have a timeout after a few seconds and report back the line/character causing the problem. If not that, then just a generic error message would be an improvement.
When your code (inside double curly braces) isn't resolving correctly (e.g. because of an extra closing curly brace) the entire expression including the curly braces just outputs as a string instead.
This should have its own error message, instead of the string output.