-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUGFIX: Support slashes in texts property #13
BUGFIX: Support slashes in texts property #13
Conversation
84e0c73
to
d7a3c8a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Looks good. What is your question? |
@jonnitto the ongoing discussion with @grebaldi is wether the string content in afx is a string or fusion-string. The escaping in jsx behaves mostly like afx already does. This also affects the related question what kind of comments should be supported in afx from. I agree with @grebaldi that we should be as intuitive for editors with jsx background. However i would be fine with adding behavior such devs would consider better as jsx. |
I will merge this soonish and release togehter with @path as 1.1.0. |
Previously only single quotes were escaped in afx text nodes. This change introduces a more generic escaping via addslashes that includes slashes, single- and double-quotes. That way the rendered result of afx will match the expectation better. resolves: neos#2
d7a3c8a
to
ef6d3d0
Compare
…ndStrings BUGFIX: Support slashes in texts property
Previously only single quotes were escaped in afx text and string nodes. This changes
introduces a more generic escaping via addslashes that includes slashes, single- and double-quotes.
That way the rendered result of afx should match the expectation better.
resolves: #2