-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Use bisq2 rest infrastructure for daonode #6228
Use bisq2 rest infrastructure for daonode #6228
Conversation
@ghubstan Could you review? |
1 similar comment
@ghubstan Could you review? |
daonode/src/main/java/bisq/daoNode/error/CustomExceptionMapper.java
Outdated
Show resolved
Hide resolved
daonode/src/main/java/bisq/daoNode/endpoints/ProofOfBurnApi.java
Outdated
Show resolved
Hide resolved
daonode/src/main/java/bisq/daoNode/endpoints/ProofOfBurnApi.java
Outdated
Show resolved
Hide resolved
daonode/src/main/java/bisq/daoNode/DaoNodeRestApiApplication.java
Outdated
Show resolved
Hide resolved
I've done one pass (review) through all the classes in the bisq.daonode package. Swagger works -- nice! |
@ghubstan Thanks for the review! |
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.
utACK - based on #6228 (comment)
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.
NACK - I just recognized that with this PR also the verification of new dependencies failed, but didn't result the build to fail.
Please also update the verification-metadata.xml
by running ./gradlew --write-verification-metadata sha25
and verify the hashes generated.
@chimp1984 Could you please resolve the conflicts by rebasing to master and re-running the verification-metadata generation? Thanks! |
66e6654
to
bbf7987
Compare
Done. |
No description provided.