-
Notifications
You must be signed in to change notification settings - Fork 101
Add version to payment information #662
Conversation
dino-rodriguez
left a comment
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.
LGTM!
0xASK
left a comment
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.
LGTM just one refactor Q
|
|
||
| const USER = '/alice' | ||
| const PAYID = `${USER.slice(1)}$127.0.0.1` | ||
| const VERSION = '1.1' |
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.
Can we establish a global const like this one in the rest of the test files in this PR so that we are always using VERSION instead of typing out '1.1' for each?
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.
Any chance we can do this refactor in a subsequent PR so we can get this release cut?
|
Actually one comment - I noticed that you mentioned we don't need version negotiation. That means that when we go from 1.x to 2.0, we are going to break the network, right? |
Co-authored-by: Dino Rodriguez <dinoorodriguez@gmail.com>
Co-authored-by: Dino Rodriguez <dinoorodriguez@gmail.com>
This reverts commit f79115d.
High Level Overview of Change
Adds a
versionkey to the PaymentInformation response payload.Context of Change
This is needed to cut the
PayID-VersionandPayID-Server-Versionheaders from the PayID Protocol when we hit 2.0. I spoke with Aanchal about versioning, and she and I came to the conclusion that (for the moment) we don't even need version negotiation, so we don't need to build out versioning in the PayID Discovery WebFinger JRD like I suggested. You can get all the information you need to know from theversionkey in the payload itself, and (hopefully) there shouldn't be many major version changes for the foreseeable future after we cut 2.0.Type of Change
Before / After
The PaymentInformation response payload now includes a
versionkey of the formversion: MAJOR.MINOR.Test Plan
Tests have been updated and all tests pass.