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

refactor(connector-quorum) connector refactor, consolidate transaction invocation API #610

Closed
kikoncuo opened this issue Mar 1, 2021 · 2 comments · Fixed by #681
Closed
Assignees
Labels
dependent Quorum Significant_Change Applying this label triggers the more stringent review of the maintainers and the 2+1 PR rule.
Milestone

Comments

@kikoncuo
Copy link
Contributor

kikoncuo commented Mar 1, 2021

Parent: feat(cactus): Standardized common interface functionality transaction across connectors #604

Description:
Update the spec for Quorum to meet the standard as defined in the parent issue.

Acceptance criteria:

OpenAPI spec meets definition as specified in the parent
Update existing references (Demo site, tests, HTLCs)
All tests passing

Depends on #612
Depends on #613

@kikoncuo kikoncuo added Quorum Significant_Change Applying this label triggers the more stringent review of the maintainers and the 2+1 PR rule. labels Mar 1, 2021
@kikoncuo kikoncuo added this to the v0.5.0 milestone Mar 1, 2021
@github-actions
Copy link

github-actions bot commented Mar 1, 2021

⏳ Alright! Looks like we need to wait for some dependencies:

💡 Don't worry, I will continue watching the list above and keep this comment updated. To add or remove a dependency please update this issue/PR description.

Brought to you by Dependent Issues (:robot: ). Happy coding!

@AzaharaC
Copy link
Contributor

AzaharaC commented Mar 2, 2021

working on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependent Quorum Significant_Change Applying this label triggers the more stringent review of the maintainers and the 2+1 PR rule.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants