-
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
R4R: Implement fee distribution RESTful endpoints #3460
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #3460 +/- ##
===========================================
+ Coverage 52.95% 54.67% +1.72%
===========================================
Files 137 139 +2
Lines 10746 10375 -371
===========================================
- Hits 5691 5673 -18
+ Misses 4705 4343 -362
- Partials 350 359 +9 |
Tested:
|
51b2b11
to
7e5e0c2
Compare
@cwgoes can you shed some light on this please? Either something is missing here, or frontend ICS24 specs need update. Note that presently {
"community_pool": [
{
"denom": "stake",
"amount": "1932.480000000000000000"
}
]
} |
All GET endpoints are now complete. Please test @cosmos/cosmos-ui. @faboweb @fedekunze @sabau Note that specs are changed, @cwgoes reviewed and updated them. I'd suggest you regenerate swagger docs and validate endpoints compliance against the new interfaces. Please keep me posted |
2ac3c64
to
87c4a0d
Compare
Progress tracking:
|
d571e69
to
010540f
Compare
How to test the PR
$ gaiad init --moniker=[YOUR_MONIKER_HERE]
Now, modify
$ gaiacli keys add foo
$ gaiad add-genesis-account foo 10000000stake # 10 mln
$ gaiad gentx --name=foo --amount=500000stake # 0.5 mln
$ gaiad collect-gentxs
$ gaiad start
|
just to go quicker I scripted the boot process if anyone is interested in playing on the parameters |
I haven't finished all the rounds. Generally the errors and some return values are plain strings so not json parsable. The behaviour seems to work but I need a bit more time Regarding the errors (null string or plain text anyway) I think is something not related to this PR but generic. |
@jackzampolin I think Karoly is talking about JSON error responses. I'll open a PR about it |
010540f
to
258536b
Compare
Exaclty, I imagine everything produced by an API to be consumable by a client that interpret only that format (let it be xml, json, ...). If an error occurs it shuold be interpretable too, otherwise every client will have to implement those special cases |
@@ -0,0 +1,143 @@ | |||
package common |
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.
nice 👍 common module
258536b
to
0e9504c
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.
Look great @alessio -- I left a minor comment, but overall it looks solid. The localnet
CI task is failing. Also, correct me if I'm wrong, but there aren't any LCD tests, so have all the endpoints been tested?
Would be great if you can add unit tests (GET and POST) for the happy paths at the endpoint: If you are running out of time I can ask @faboweb if I can borrow some Voyager hours to write unit tests to cover the others. Manually so far so good! |
[@alessio]
[@rigelrozanski ]
Closes: #3476
Closes: #2358
Closes: #3490
docs/
)PENDING.md
with issue #Files changed
in the github PR explorerFor Admin Use: