We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The engine is unable to properly close a tag if the ending tag has a different casing from the start tag.
For example:
[div style="border: 1px solid red"] lorem ipsum [/DIV]
gets parsed to
[ { "tag": "div", "attrs": { "style": "border: 1px solid red" }, "content": [] }, "\n", "lorem", " ", "ipsum", "\n" ]
On a secondary note: the orphaned closing tag is not added back into the output as plain text, giving the impression that it was accepted.
The text was updated successfully, but these errors were encountered:
feat(#250): introduce caseFreeTags option (#251)
ccab54a
* chore: initial tests * feat: parser test * feat: add case free tags support * fix: coverage upload * fix: --disable=gcov * fix: npm publish sha commit * fix: change codecov to coveralls * fix: change workflow pr build and publish * chore: change coverage badge [skip ci]
JiLiZART
Successfully merging a pull request may close this issue.
The engine is unable to properly close a tag if the ending tag has a different casing from the start tag.
For example:
gets parsed to
On a secondary note: the orphaned closing tag is not added back into the output as plain text, giving the impression that it was accepted.
The text was updated successfully, but these errors were encountered: