Skip to content
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

Closed
5 of 6 tasks
bajtos opened this issue Jun 21, 2018 · 4 comments
Closed
5 of 6 tasks

[Epic] KeyValue repository #1447

bajtos opened this issue Jun 21, 2018 · 4 comments

Comments

@bajtos
Copy link
Member

bajtos commented Jun 21, 2018

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

The use case to drive the features: a "shopping cart" component used on an e-shop platform like Walmart.

@bajtos bajtos added the epic label Jun 21, 2018
This was referenced Jun 21, 2018
@bajtos bajtos changed the title Epic: KeyValue repository [Epic] KeyValue repository Jun 25, 2018
@raymondfeng
Copy link
Contributor

The runtime support is added - #1539

@bajtos
Copy link
Member Author

bajtos commented Aug 23, 2018

Please note that the runtime implementation has a flaw we need to address, preferably before considering this feature as done. See #1539 (comment):

Ideally, I'd like our DefaultKeyValueRepository to leverage the same mechanism that DefaultCrudRepository uses:

  • The backing model has the same name as the LB4 model.
  • If the datasource already has a backing model defined, then we reuse it.
  • When defining a new backing model, LB4 property definition is converted to juggler schema.

@raymondfeng
Copy link
Contributor

Adding docs - #1654

@dhmlau
Copy link
Member

dhmlau commented Sep 4, 2018

The docs task has been created and PR has merged. Closing this task as resolved.

@dhmlau dhmlau closed this as completed Sep 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants