Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extract Parser into its own NPM package to allow the client to test future templates. #127

Open
Flintonian opened this issue May 19, 2022 · 1 comment

Comments

@Flintonian
Copy link
Collaborator

Flintonian commented May 19, 2022

  • Plan is to split out the parser into its own NPM package and host a public repo on devetry.
  • Task needed especially as we are building to a moving target.
  • CI to ensure changes merged to branch 157 (our branch) do not break existing code.
@Flintonian Flintonian changed the title Extract Parser into it's own NPM Pkg Extract Parser into it's own NPM Pkg (this will allow them to test future templates) Jun 6, 2022
@yvesgurcan
Copy link
Collaborator

@Flintonian It looks like this could be something for me to tackle while waiting for the client to refine the requirements for the Sequence Document (#31). What do you think?

@yvesgurcan yvesgurcan changed the title Extract Parser into it's own NPM Pkg (this will allow them to test future templates) Extract Parser into its own NPM package to allow the client to test future templates. Jun 28, 2022
@Flintonian Flintonian added this to the 09: Clean Up/Documentation milestone Aug 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants