-
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
[Epic] KeyValue repository #1447
Comments
This was referenced Jun 21, 2018
Closed
4 tasks
The runtime support is added - #1539 |
Please note that the runtime implementation has a flaw we need to address, preferably before considering this feature as done. See #1539 (comment):
|
Adding docs - #1654 |
The docs task has been created and PR has merged. Closing this task as resolved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So far, LB4 persistence story is all about CRUD. Key-value stores are another common scenario we should support.
LoopBack 3.x introduced KeyValue API and Redis + eXtremeScale connectors.
For LoopBack 4, we need to add Repository implementations for KeyValue API and verify that all pieces work together as expected.
Scope
lb4 repository
command #1588)The use case to drive the features: a "shopping cart" component used on an e-shop platform like Walmart.
The text was updated successfully, but these errors were encountered: