-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add JSON Spec to sequencing server #616
Add JSON Spec to sequencing server #616
Conversation
8f89db5
to
7a1396e
Compare
7a1396e
to
09375a1
Compare
09375a1
to
23966f8
Compare
23966f8
to
bce4b9c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me too, we'll need to coordinate with my PR #617 since we have some overlap that'll need to be resolved.
@cohansen Yeah, I think merge your PR first and I will rebase this one. |
This is to avoid the namespace collision with the JSON Spec.
Now the commandLib has both the spec and edsl.
bce4b9c
to
f625d8b
Compare
Description
The overall goal is to incorporate the JSON spec into the Aerie Repo and give eDSL access to the full JSON Spec while wrapping the current EDSL into the 4 command types. The goal is to clean up the code and merge more of the spec and EDSL API together to create a tighter coupling, and to look at how to write custom eDSL to make the process easier.
This is the first part of the development process, which will be to add the JSON spec to the Aerie Repo and combine it with the EDSL.
Verification
I ran through the e2e tests without any issues.
Documentation
None
Future work
Rework the Sequence eDSL class with this new spec file.