Hybrid tree formatting + link mapping #645
Closed
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.
why
what changed
StaticText
nodes into their parent node when possibleStaticText
nodes if they are a child of alink
[@id]
TreeResult
type now holds anidToUrl
dictionary where node IDs are keys and URLs are valuesexample
here is what the tree looked like before:
here is what the tree looks like now:
future PRs (fast follow)
idToUrl
mapping, and include that in the extraction resulttext_extract
, just have oneextract
functiontest plan