The response in the RPC result startTime is camel cased while the rest of the response seems to be lower cased.
If this was intentional please ignore and close this PR.
Note: RPC field case changes might break existing callers
The response in the RPC result startTime is camel cased while the rest of the response seems to be lower cased.
If this was intentional please ignore and close this PR.
Note: RPC field case changes might break existing callers
Note: RPC field case changes might break existing callers
Right, NACK for that reason.
The interface was broken in this release anyway. So might as well fix it up. I have no opinion on which one should be preferred.
@MarcoFalke oh ok.
I think starttime is ok. @dangershony can you please squash your commits.
ACK f057b5f4479f00d0947eade2cd5bbb1acce49ded
from the RPC interface guidelines:
- Argument naming: use snake case
fee_delta(and not, e.g. camel casefeeDelta)
ACK (well it's not snake case, start_time would be even better maybe, but anyhow we shouldn't use camel case in RPC fields)
ACK f057b5f4479f00d0947eade2cd5bbb1acce49ded (I am fine with start_time as well)
ACK either but prefer start_time (2 words, snake case, no way to get it wrong)
Ok, added "waiting for author" label @dangershony ^
I will make the changes hang on.
The response in the RPC result `starttime` is camel cased while the rest of the response seems to be lower cased.
If this was intentional please ignore this PR.
Note: case might break existing callers
Reflect the change in the test data
Change to snake case
ACK 1a02edb3f2803b6f82f06a31acf0b0e5fc19bd1c