Roadmap update reg. parsing #83
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is mainly motivated to decouple earlier from lxml, so that it isn't a burden when refactoring to the native implementation and to be more confident that the result will have a stable API.
funkyfuture
commented
Apr 16, 2024
| - or explicity `parse_one_node` and `parse_multiple_nodes`? | ||
| - the tree building will be based on (SaX-like) event parsers for which a common | ||
| abstract interface needs to be defined, considering concrete implementations of | ||
| adapers for: |
There was a problem hiding this comment.
Suggested change
| adapers for: | |
| adapters for: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
since i had several questions and ideas on that topic on my head, i put these aside into
ROADMAP.md.