Update relay status check to use relayMetadata.orderId and use v2 protocol for anything
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Start by locating the relay status check and quote status fetching code, then trace how relayMetadata.orderId and the v2 protocol are handled. Done means relay quote status fetching works after the v2 migration and uses the requested orderId and protocol behavior.
Written by the indexing model from the issue text.
Description
Migrating to v2 will break quotes status fetching for relay, we need to fix it by using orderId I guess and update to the v2 protocol anything!
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 9h 59m
- Merged PRs (30d)
- 12
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from shapeshift/microservices
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
shapeshift/microservices#64 ·
All issues in shapeshift/microservices
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·