-
Notifications
You must be signed in to change notification settings - Fork 217
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
API specification for multi-asset wallet migration #2590
Conversation
246150e
to
16f7eb4
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.
Looks reasonable, I think
In response to review feedback: #2590 (comment)
23594eb
to
f21643f
Compare
f21643f
to
65e154b
Compare
65e154b
to
34f56cd
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.
There should also be updates to the getShelleyWalletMigrationInfo
and migrateShelleyWallet
specs, right?
2099f94
to
c9470ca
Compare
697f0f2
to
202e024
Compare
Hi @rvl
I plan to update the description of this endpoint in the next PR, when the algorithm is connected up to the API. (We'll have to update the description then anyway, in order to remove the " As for their return types, these currently both have the same return types:
These both return a
I wasn't planning to change the type of this endpoint in any way, as it currently returns a list of transactions, which seems to be exactly what we need. But perhaps you've thought of something that I've missed? |
In The description of |
c650885
to
5e9a20a
Compare
Hi @rvl I've updated the descriptions in this pair of commits: |
5e9a20a
to
76c0867
Compare
c9470ca
to
e687560
Compare
We'll eventually need the `ApiWalletMigrationInfo` record to encode two different types of balance: - balanceSelected - balanceLeftover
76c0867
to
3e14fb4
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.
Nice thanks - better now.
bors r+ |
2590: API specification for multi-asset wallet migration r=rvl a=jonathanknowles # Issue Number ADP-840 # Overview This PR revises the **_API specification_** to support multi-asset wallet migrations. The **_server implementation_** will be added in a subsequent PR. (Connecting the API with the algorithm.) # Details This PR: - [x] Adds a `ApiWalletMigrationBalance` type: ```yaml ApiWalletMigrationBalance: &ApiWalletMigrationBalance type: object required: - ada - assets properties: ada: *amount assets: *walletAssets ``` - [x] Revises the `ApiWalletMigrationInfo` type: ```yaml ApiWalletMigrationInfo: &ApiWalletMigrationInfo type: object required: - selections - total_fee - balance_leftover - balance_selected properties: selections: type: array items: *ApiCoinSelection total_fee: <<: *amount balance_leftover: <<: *ApiWalletMigrationBalance balance_selected: <<: *ApiWalletMigrationBalance ``` Co-authored-by: Jonathan Knowles <[email protected]>
Build failed: Looks like something weird happened while attempting to start the build. (i.e., not an actual test failure.) |
bors r+ |
Right, that bors failure was correct. This was the error message:
|
Perhaps it's because of a race condition? The branch of this PR was originally based on If branch But if bors attempts to build before this happens, then it will fetch something that's not yet based on When I did |
Yes - a race, sort of. Bors would have created the merge commit for the next batch before it got notification from GitHub that the PR base branch changed. |
Build succeeded: |
Issue Number
ADP-840
Overview
This PR revises the API specification to support multi-asset wallet migrations.
The server implementation will be added in a subsequent PR. (Connecting the API with the algorithm.)
Details
This PR:
Adds a
ApiWalletMigrationBalance
type:Revises the
ApiWalletMigrationInfo
type: