-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Split model-config.json into multiple files #1316
Comments
Someone post the same question at stackoverflow |
Thank you for reporting this idea, it makes sense to me. Perhaps we can modify loopback-boot to load model configuration from |
@bajtos |
+1 |
Looking forward to having this. What's the status? |
+1 |
+1 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the |
model-config.json become too complex when having tons of models to be configured.
imagine that we have 30 to 50 models to be configured in 'model-config.json',
the file will become complex and hard to read.
I think loop-back should separate the model configurations by model, just like how we define the model itself.
Tasks
The text was updated successfully, but these errors were encountered: