-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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 long-deprecated account_tx switch #2926
Comments
@mDuo13 @scottschurr For the command line, there are really only two fields that require calling the legacy handler: count and offset. I propose we simply ignore these fields if they are present, and include a warning in the response. The other legacy fields can be easily mapped to a non-legacy field: descending is the same as forward. ledger_min and ledger_max are the same as ledger_index_min and ledger_index_max. Since the command line version parses arguments based on position, as opposed to the fields being named, we can just interpret these legacy values as their non-legacy analogues. |
I'm all in favor of it. |
The switch for the legacy code was removed as part of #3609. However, some of the old code is still lingering around, e.g. https://github.com/ripple/rippled/blob/master/src/ripple/rpc/handlers/AccountTxOld.cpp |
(Porting this issue from Ripple's internal Jira ticket RIPD-1569)
Description
The account_tx method has an "old" mode that's been deprecated since at least 2013, with a "temporary switch" to use the old mode if people provide certain parameters (offset, count, descending, ledger_max, or ledger_min) in the request, and the new mode otherwise.
I'd say it's about time to remove the old mode.
Blocker
Per @scottschurr:
The text was updated successfully, but these errors were encountered: