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

lcd test cleanup #625

Merged
merged 3 commits into from
Mar 18, 2018
Merged

lcd test cleanup #625

merged 3 commits into from
Mar 18, 2018

Conversation

ebuchman
Copy link
Member

@faboweb faboweb force-pushed the fabo/383-rest-server branch from ba6ec0a to 16ceca6 Compare March 15, 2018 10:44
@ebuchman ebuchman force-pushed the fabo/383-rest-server branch from 8c51cee to 683663f Compare March 17, 2018 22:08
@ebuchman ebuchman force-pushed the bucky/lcd-test-cleanup branch from f88d43c to d807d32 Compare March 17, 2018 22:09
@ebuchman ebuchman changed the title WIP: lcd test cleanup lcd test cleanup Mar 18, 2018
@ebuchman ebuchman force-pushed the bucky/lcd-test-cleanup branch 2 times, most recently from b9cbfe9 to 6485213 Compare March 18, 2018 00:58
@codecov
Copy link

codecov bot commented Mar 18, 2018

Codecov Report

Merging #625 into fabo/383-rest-server will decrease coverage by 2.74%.
The diff coverage is 56.79%.

@@                   Coverage Diff                    @@
##           fabo/383-rest-server     #625      +/-   ##
========================================================
- Coverage                 65.87%   63.13%   -2.75%     
========================================================
  Files                         8       38      +30     
  Lines                       378     2094    +1716     
========================================================
+ Hits                        249     1322    +1073     
- Misses                      102      666     +564     
- Partials                     27      106      +79

@ebuchman ebuchman merged commit 10f50a3 into fabo/383-rest-server Mar 18, 2018
@ebuchman ebuchman deleted the bucky/lcd-test-cleanup branch March 18, 2018 01:13
@ebuchman
Copy link
Member Author

@adrianbrink @rigelrozanski @faboweb see how I set up the Tendermint/LCD in process here.

Could still use some love :)

// into the app right away (#565)
if chainID == "" {
chainID = viper.GetString("chain-id")
}
signBytes := sdk.StdSignBytes(ctx.ChainID(), sequences, fee, msg)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you set chainID in line 50 but use ctx.ChainID() here again.

@faboweb
Copy link
Contributor

faboweb commented Mar 19, 2018

Amazing work. Thanks a lot. Sorry to see it was still that much todo.

@mappum
Copy link
Contributor

mappum commented Mar 19, 2018

In the sendtx endpoint, is there a reason the address comes from the querystring and not the body?

type sendBody struct {
// fees is not used currently
// Fees sdk.Coin `json="fees"`
Amount sdk.Coins `json:"amount"`
LocalAccountName string `json:"name"`
Password string `json:"password"`
ChainID string `json:"chain_id"`
Sequence int64 `json:"sequence"`
}
// SendRequestHandler - http request handler to send coins to a address
func SendRequestHandler(cdc *wire.Codec, kb keys.Keybase) func(http.ResponseWriter, *http.Request) {
c := commands.Commander{cdc}
return func(w http.ResponseWriter, r *http.Request) {
// collect data
vars := mux.Vars(r)
address := vars["address"]

@mappum
Copy link
Contributor

mappum commented Mar 19, 2018

NVM, it's in the URL path, that makes sense 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants