For simplicity, the parser has been developed as part of the same project. This allowed for a faster development cycle as parser features were able to be implemented the by the UI in the same PR.
To allow the parser to be reused by other projects, and to separate concerns, the parser from Lincoln should be pulled out into it's own package.
This would be a good opportunity to switch to Typescript and have a rethink if the current implementation is scalable moving forward. I'd suggest doing #106 as a precursor to this ticket.
#146 would likely move to that project too.
For simplicity, the parser has been developed as part of the same project. This allowed for a faster development cycle as parser features were able to be implemented the by the UI in the same PR.
To allow the parser to be reused by other projects, and to separate concerns, the parser from Lincoln should be pulled out into it's own package.
This would be a good opportunity to switch to Typescript and have a rethink if the current implementation is scalable moving forward. I'd suggest doing #106 as a precursor to this ticket.
#146 would likely move to that project too.