-
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
Integration with TypeORM #4853
Comments
This is awesome. I know a lot of people use Mongoose, and TypeORM; the user story that you can bring your current ORM/ODM experience to your loopback application is a powerful one. How do we feel about having a more concrete example, than provided in the acceptance tests? For example, the most basic loopback application possible, built to showcase using TypeORM (in this case)? I'm not saying every single feature typeorm provides needs to be highlighted, but just enough of a basic structure (some models, maybe a couple of different connections to different databases). And is the PR a good place for discussion, or is this issue more appropriate? |
I think an example would be great. Do you mean to use the TypeORM component in #4794 and create an example on how to use it? |
cc @raymondfeng |
Probably with complete endpoint example from controller, model, repository including on how to create openapi schemas using decorators. I have tries this example, only place I struggled was to frame openapi schemas for "filters" using decorators with typeorm. |
@raj-298585 Thank you for chiming in - we have some prior efforts to transform LB repository apis into TypeORM implementation - see #763. I'll spend some time to build an e2e acceptance test and go from there. |
I need that, actually I use TypeORM in Lb3 :) |
Good i need this also 👍, |
You mean |
I mean |
Yep. |
We are impatiently awaiting this development, |
Targeting for landing some time coming week, no promises though. |
Closing as done |
By default, LoopBack juggler is used. LoopBack also has the flexibility to integrate other ORMs, like TypeORM. There is an existing PR #4794
Acceptance Criteria
The text was updated successfully, but these errors were encountered: