preliminary working integration with parser backend#51
Merged
Conversation
bbonf
force-pushed
the
feature/parse-interface
branch
from
554bb48 to
19e7f5e
Compare
This was referenced Mar 17, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 is very much still WIP
The major offense is that the CCG tree rendering code is copy-pasted from the tableau rendering code. This will be refactored to use a shared tree-rendering (set of) component(s).
Otherwise there's some thinking to be done about the component hierarchy and flow of data. E.g. hooking up the form data to the parent AnnotateComponent.