You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to avoid adding duplicate style/script tag patterns and avoid possible conflicts with updated core HTML syntax a Vue syntax for ST4126+ with obsolete contexts removed should be created and released separately.
Various contexts are marked "required until 4113" as they have been added in ST4114. I'd suggest to use the next available stable build 4126 as waypoint to provide a backward-incompatible syntax.
Yes, I am perfectly fine with this decision. We just need to create a branch before introducing backwards-incompatible changes and imo targetting the next stable version is a fine choice. 4126 was over 3 years ago anyway.
I don't remember the various core syntax changes breakpoints by heart. Has anything else worthwhile been done to the default syntaxes since then that could warrant another breakpoint?
It's crucial for proper indentation of script/style content and also may be worth applying to template tags.
So if we keep all related variables and copy patterns from liked PR, we shouldn't need another breakpooint. All the other fixes should apply automatically for newer ST builds.
Resolves#9
Primary goal: Avoid duplicate `script` and `style` tag patterns in `tag-html` context.
It removes all contexts, which are present only for backward compatibility with ST4107..4113.
In order to avoid adding duplicate style/script tag patterns and avoid possible conflicts with updated core HTML syntax a Vue syntax for ST4126+ with obsolete contexts removed should be created and released separately.
Various contexts are marked "required until 4113" as they have been added in ST4114. I'd suggest to use the next available stable build 4126 as waypoint to provide a backward-incompatible syntax.
requires: #7
The text was updated successfully, but these errors were encountered: