Change RangeMap to be a hierarchy of structures with entries #51
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.
This PR changes much of way RangeMap is built and how RangeAplier uses it to process java source file. RangeMap specification stays same.
At first, it changes data model of RangeMap:
Secondly, this changes RangeApplier to process RangeMap:
By processing it mean:
= if child is just RangeEntry it does same action like previously - replaces text occurence in output string
= if child is a StructuralEntry it does processing "from start" (like starting from ROOT)
In each case all tests passes. It needed to correct some patterns (misplaced entries).
I don't know how you planned to do this kind of feature, but i think my solution will be very comfortable to expand processing functionality in future. This is good start to other features such:
If something is unclear or need to correct, please give me feedback.