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
When evaluating an expression that has an attribute, the current lexer in the parser-fixes2 branch allows matching spaces as part of the tag name. This prevents the Lexing State from moving to lexing the attributes, instead giving an error when it reaches the = character.
Example: running ezno ast-explorer ast and using the expression <div className="test"></div>
Output:
error:
┌─ INPUT:1:2
│
1 │ <div className="test"></div>
│ ^ Invalid character '=' in JSX tag
When removing the match on spaces here it allows the lexer to continue onto the attribute lexing state, giving the following output for the same example:
I have a fork with the changes made to the parser-fixes2 branch here, but wanted to double check that there wasn't a reason to be lexing spaces as part of the tag name first.
Thank you :)
The text was updated successfully, but these errors were encountered:
When evaluating an expression that has an attribute, the current lexer in the parser-fixes2 branch allows matching spaces as part of the tag name. This prevents the Lexing State from moving to lexing the attributes, instead giving an error when it reaches the
=
character.Example: running
ezno ast-explorer ast
and using the expression<div className="test"></div>
Output:
When removing the match on spaces here it allows the lexer to continue onto the attribute lexing state, giving the following output for the same example:
I have a fork with the changes made to the parser-fixes2 branch here, but wanted to double check that there wasn't a reason to be lexing spaces as part of the tag name first.
Thank you :)
The text was updated successfully, but these errors were encountered: