ZO-4627: Use lxml.etree for content objects instead of lxml.objectify #626
Commits on Feb 21, 2024
-
-
ZO-4627: Search and replace lxml.objectify with lxml.etree (except fo…
…r config sources)
-
-
ZO-4627: Since the whole point is to preserve whitespace, we have to …
…do our own pretty printing for tests See https://lxml.de/FAQ.html#why-doesn-t-the-pretty-print-option-reformat-my-xml-output
-
ZO-4627: Source edit cannot pretty print anymore, either
In the future, we might want to mark nodes/subtrees that contain significant whitespace (e.g. article body, markup text etc.), so that we can still pretty print anything else.
-
-
-
ZO-4627: Ignore trailing whitespace in wysiwyg subtrees
Result changed from '<p>bar!</p>\n' to '<p>bar!</p>\n \n', and it's a bit unclear why.
-
-
-
MAINT: Remove unused parameter
This has existed since forever (762326d) but was not used even then. It's unclear if in the interim there used to be some subclass that used it, but anyway nowadays there isn't, so begone!
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.