-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
remove ICS categories from swagger #4429
Conversation
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.
ACK
@hschoenburg we now commit the generated statik file. Please run: |
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.
ACK -- needs swagger docs build updated.
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.
Thanks Hans ! Few things missing:
/auth/accounts/{address}
is still underICS1
tag, should have tagAuth
- Missing
Mint
tag for mint requests GET /node_info
is duplicated, need to delete the one withMisc
tag
1eddbd5
to
6e85558
Compare
Thanks for the comments guys. I added a newly generated statik.go, as well as Auth and Mint tags. @fedekunze I wasn't completely clear on which |
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.
ACK
|
6e85558
to
ee3c2e6
Compare
sorry forgot to fix the statik.go check until now. Lmk if there is anything more I can do here. Looks like the PR needs to be merged locally because of the statik.go conflict. |
There is a conflict @hschoenburg. Perhaps the statik file you generated should be the one committed. How did you generate it? |
@alexanderbez >> thanks for following up. Since this PR makes changes to the swagger.yaml I imagine the statik.go in this branch is the one that should be merged into master. After committing the changes to swagger.yaml I ran |
That is the correct process @hschoenburg -- simply commit your |
Shouldn't we remove also the implementation along with the documentation? Or we end up having those two working but not documented:
|
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.
need to resolve conflicts and add clog
entry
@hschoenburg can we have this for the release next week? |
Codecov Report
@@ Coverage Diff @@
## master #4429 +/- ##
=======================================
Coverage 52.75% 52.75%
=======================================
Files 264 264
Lines 16464 16464
=======================================
Hits 8685 8685
Misses 7130 7130
Partials 649 649 |
f1b6e75
to
288582d
Compare
decided to not add a clog entry, spoke with team in berlin |
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.
ACK -- no pending log entry needed imho.
also, the commit message steemed from something else I apologize for it |
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
Targeted PR against correct branch (see CONTRIBUTING.md)
Linked to github-issue with discussion and accepted design OR link to spec that describes this work.
Wrote tests
Updated relevant documentation (
docs/
)Added a relevant changelog entry:
clog add [section] [stanza] [message]
rereviewed
Files changed
in the github PR explorerFor Admin Use: