Template parsing errors are separated from structural errors. For structural issues like unclosed tags or having multiple root-level elements, a new error type called TemplateStructureError has been introduced.
Now, the error messages give more details. They show the component name, the parent component (when precompile is off), and the component's file path (when precompile is on). This helps to know where the error is happening.
Template parsing and structural errors are critical and can no longer be suppressed. So, encountering these errors will now halt the application to ensure that those issues are addressed.
When an error occurs, the error message will also show where in the template the problem (roughly) is. This makes it easier to find and fix the issue.
Fixes an issue where closing tags with attributes were incorrectly accepted. Now, the parser can catch this kind of problem too.
Template parsing errors are separated from structural errors. For structural issues like unclosed tags or having multiple root-level elements, a new error type called
TemplateStructureErrorhas been introduced.Now, the error messages give more details. They show the component name, the parent component (when precompile is off), and the component's file path (when precompile is on). This helps to know where the error is happening.
Template parsing and structural errors are critical and can no longer be suppressed. So, encountering these errors will now halt the application to ensure that those issues are addressed.
When an error occurs, the error message will also show where in the template the problem (roughly) is. This makes it easier to find and fix the issue.
Fixes an issue where closing tags with attributes were incorrectly accepted. Now, the parser can catch this kind of problem too.
How errors are displayed
When precompile is off
When precompile is on