Skip to content
This repository has been archived by the owner on Feb 23, 2024. It is now read-only.

Checkout Block REST API: What routes/endpoints are needed? #1212

Closed
nerrad opened this issue Nov 19, 2019 · 2 comments
Closed

Checkout Block REST API: What routes/endpoints are needed? #1212

nerrad opened this issue Nov 19, 2019 · 2 comments

Comments

@nerrad
Copy link
Contributor

nerrad commented Nov 19, 2019

In this exploration, a review should be taken of our existing endpoints and routes and clarify what we have vs what we think we'll need.
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label type: feature request to this issue, with a confidence of 0.54. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@nerrad nerrad added type: cooldown Things that are queued for a cooldown period (assists with planning). and removed type: feature request labels Nov 19, 2019
@nerrad nerrad added type: feature request and removed type: cooldown Things that are queued for a cooldown period (assists with planning). labels Dec 2, 2019
@nerrad nerrad changed the title Exploration: Checkout Block: What routes/endpoints are needed? Checkout Block: What routes/endpoints are needed? Dec 2, 2019
@nerrad nerrad changed the title Checkout Block: What routes/endpoints are needed? Checkout Block REST API: What routes/endpoints are needed? Dec 2, 2019
@nerrad
Copy link
Contributor Author

nerrad commented Dec 7, 2019

Closing this in favor of the #1312 epic.

@nerrad nerrad closed this as completed Dec 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nerrad