-
Notifications
You must be signed in to change notification settings - Fork 1
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
SIWF v2 Process Payloads #600
Conversation
37b1d35
to
d99e06c
Compare
d9aa75e
to
f815dd7
Compare
expect(response.body).toHaveProperty('rawCredentials'); | ||
}); | ||
|
||
// TODO: Is there a way to mock the fetch in the e2e? |
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.
Is there a way to do this? I don't think there is which means we would need to setup a mock server.
Worth doing it? I can do it fairly easily as we already have a mock server system and clean response json
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.
If the merge is not urgent then I feel it will be nice to have your piece of mock server already in place, will come handy as we develop more.
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.
I'll see what I can do on Monday.
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.
Added!
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.
- Read through changes
- Tested example, saw log messages flowing (authorizationCode was invalid, maybe that's expected for testing?)
🚢 it!
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.
Read through the code, looks good 💯
That was expected. |
# Problem Missed generating the openapi json for the new siwf v2 endpoint. Missed in #600
Problem
We want to process the SIWF v2 payloads. Authenticate the user, and process chain interactions.
Closes #526
Closes #527
Closes #529
Solution
Processed the data using SIWF v2 library and then built the extrinsics to re-use the same queue as SIWF v1.
Steps to Verify:
docker compose up redis
npm run start:account-api:dev
npm run start:account-worker:debug
node tools/siwfv2/example.mjs