-
Notifications
You must be signed in to change notification settings - Fork 450
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
XML treated as HTML for beautification #197
Comments
@Glavin001 you could use Pretty Diff for XML beautification. The markup parser in Pretty Diff was written to support XML first and then HTML support was added with an option on top of the XML parser. This is mostly seamless if using Pretty Diff's language auto-detection. |
Definitely want to use PrettyDiff. Thanks for heads up! |
@prettydiff will handle XML in the next release (see #282). |
What's new: - Beautifier options definition supports: - boolean - enable/disable - string - rename and enable - function - transform and enable - array - apply complex transformation to multiple options and output single option result - Show "Supported by <beautifiers>" for each language option - Beautifiers have a name - Beautifier options definition is used to determine if language option is supported by a beautifier - Remove SQL test, since sqlformat is inconsistant
Published to v0.25.0 This is a very big release with lots of internal changes and (hopefully) no breaking changes. Please let me know if you are experiencing any unusual behaviour / breaking changes after updating. Thank you. |
#3 turned on xml beautification by treating xml as html. That solution is a hack and will be ineffective in a wide variety of cases. #158 is one example of this.
js-beautify does not support xml beautification at this time. beautifier/js-beautify#648 is the feature request for beautifying xml. That said we will attempt to fix xml related bugs as opportunity arises.
The text was updated successfully, but these errors were encountered: