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

Split model-config.json into multiple files #1316

Closed
2 tasks
mamboer opened this issue Apr 20, 2015 · 9 comments
Closed
2 tasks

Split model-config.json into multiple files #1316

mamboer opened this issue Apr 20, 2015 · 9 comments
Labels

Comments

@mamboer
Copy link

mamboer commented Apr 20, 2015

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

  • implement the feature in loopback-boot
  • modify loopback-workspace to support this new project layout
@mamboer
Copy link
Author

mamboer commented Apr 20, 2015

Someone post the same question at stackoverflow
http://stackoverflow.com/questions/27850297/loopback-spliting-model-config-json

@bajtos bajtos changed the title model-config.json become too complex when having tons of models to be configured Split model-config.json into multiple files Apr 28, 2015
@bajtos
Copy link
Member

bajtos commented Apr 28, 2015

Thank you for reporting this idea, it makes sense to me. Perhaps we can modify loopback-boot to load model configuration from server/model-config/*.json files. Would that work for you?

@mamboer
Copy link
Author

mamboer commented Apr 30, 2015

@bajtos
That will be cool!

@0xJuancito
Copy link

+1

@alexjoverm
Copy link

Looking forward to having this. What's the status?

@imravichaudhary
Copy link

+1

@siddhipai siddhipai removed the boot label Mar 27, 2017
@leonlucc
Copy link

+1

@stale stale bot added the stale label Aug 28, 2017
@stale
Copy link

stale bot commented Aug 28, 2017

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.

@stale stale bot closed this as completed Sep 11, 2017
@stale
Copy link

stale bot commented Sep 11, 2017

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 CODEOWNERS file at the top-level of this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants