htmljs-parser
Advanced tools
Changelog
5.4.1
72b3379
Thanks @DylanPiercey! - Fix regression where the parser would continue unary keyword expressions even if the keyword was inside a word boundary. Eg <div class=thing_new x>
would cause the parser to see the expression as thing_
and new x
.Changelog
5.4.0
#154 6b5b196
Thanks @DylanPiercey! - In concise mode, a new line which starts with a coma will now continue attributes for the current tag.
#154 6b5b196
Thanks @DylanPiercey! - Allow a comma to follow the tag name to begin attributes.
61e6966
Thanks @DylanPiercey! - Avoid continuing expressions after a period if after the whitespace is something that could not be an identifier.Changelog
5.3.0
ea65c9f
Thanks @DylanPiercey! - Improve handling ambiguity with tag type args vs type params. Type args must now always be directly adjacent the tag name, otherwise it will become type params.Changelog
5.2.4
0d7210b
Thanks @DylanPiercey! - Fix issue with tag variable not terminated on concise mode text delimiterChangelog
5.2.3
948830e
Thanks @DylanPiercey! - Fix issue with semi-colon after a block scriptlet.Changelog
5.2.2
bcfd809
Thanks @DylanPiercey! - Fixes an issue where attribute names that started with a keyword (eg: as-thing
or instanceof-thing
) were incorrectly treated as an expression continuation.Changelog
5.2.1
635b97c
Thanks @DylanPiercey! - Fix issue where and extra character was being consumed if an escaped placeholder was at the end of a tag.Changelog
5.2.0
81cff30
Thanks @DylanPiercey! - Add support for type parameter/argument parsing.
This adds a new onTagTypeParams
, onTagTypeArgs
events and a .typeParams
property on the AttrMethod
range.Changelog
5.1.5
8c34227
Thanks @DylanPiercey! - Fixes a parse error where division is immediately followed by enclosed code.Changelog
5.1.4
b5fa4d0
Thanks @DylanPiercey! - Optimize parser constructor to avoid initializing unecessary properties.cdbc6b2
Thanks @DylanPiercey! - Improve missing attribute error when the tag is immediately closed without the attribute value.