-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Demo scenario: Shopping Cart Component #1481
Comments
Yes, this is blocked by #1447, I am relabelling this story as |
In progress by @raymondfeng - see loopbackio/loopback4-example-shopping#4 |
The acceptance criteria don't not describe any Controller (REST API), is that intentional? IMO, a shopping cart component is not complete without a REST API to access the data. |
When I wrote the acceptance criteria it was with the intention that there will be a full CRUD controller for this component. -- This is also meant to be reflected in the estimate this task was given of an 8. My apologies for not being more specific -- but a full CRUD controller (or at least the APIs that make sense for this Model / Controller). |
No worries. I am going to edit the issue description and add a CRUD controller to the list of acceptance criteria. |
@raymondfeng Is this good to close? |
@virkt25 Please review loopbackio/loopback4-example-shopping#13 1st. |
One last piece: loopbackio/loopback4-example-shopping#14 |
Hi @raymondfeng are we ok to close the issue since 2 PRs above are merged? |
Closing as resolved. |
Description / Steps to reproduce / Feature proposal
As part of the e-commerce store demo scenario in #1476, this task is to create the Shopping Cart component. Shopping cart data will be stored in a distributed in-memory cache, e.g. Redis.
Questions:
Acceptance Criteria
The text was updated successfully, but these errors were encountered: