You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.
My application we are using TypeORM for models https://github.com/typeorm/typeorm
, however, lumber generates sequelize models files, so it means we need to keep updated the squelize models to match the models from the code base written in typeORM.
problem: hard to keep track of 2 models.
Any change to support TypeORM models?
The text was updated successfully, but these errors were encountered:
We would love TypeORM support as well! I used Forest Admin in a Rails project and loved the direct integration, so my fingers are crossed for something similar with TypeORM. I really want to use Forest Admin over building our own solution but maintaining two models likely won't make sense in the long run. It's fine for reading data, but missing out on validations and transformations when writing is the real problem.
For reference, here's how TypeORM compares to Sequelize and Mongoose in terms of npm downloads:
Sequelize and Mongoose are still the most used ORM's, but TypeORM is already at the download count that Sequelize was just a year and a half ago.
My application we are using TypeORM for models https://github.com/typeorm/typeorm
, however, lumber generates sequelize models files, so it means we need to keep updated the squelize models to match the models from the code base written in typeORM.
problem: hard to keep track of 2 models.
Any change to support TypeORM models?
The text was updated successfully, but these errors were encountered: