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 }}
Repository navigation
Extend options arg to support custom model definitions #49
Extend the options argument of boot/compile to allow the developer to supply custom model definitions (to replace the result of findModelDefinitions). Together with the existing options.models, it will allow you to specify all model-related data and still use the benefits which loopback-boot provides (most notably loading models in order defined by inheritance, i.e. base models are loaded before models that are extending them).
Thanks. I'm attempting to upgrade to loopback-boot 2.0 but this is a blocker for me. My use case is essentially model schema discovery from a custom (unsupported) database. In 1.0 I simply ran a function that modified the JSON configuration before passing to loopback-boot. I am thinking of simply implementing dataSource.discoverSchema for this custom connector - do you have any examples of that data that being merged into the models passed to loopback-boot?
I am thinking of simply implementing dataSource.discoverSchema for this custom connector - do you have any examples of that data that being merged into the models passed to loopback-boot?
My knowledge of schema discovery is very limited, @raymondfeng knows much more. I believe the result of dataSource.discoverySchema is mostly the same as the content of common/models/model-name.json.
Thanks. I'm attempting to upgrade to loopback-boot 2.0 but this is a blocker for me.
I am afraid this issue is not a priority for us at the moment, thus I won't have time to implement it anytime soon. Can you contribute the implementation yourself?
I’m going to see what I can do with discovery - from there I’ll contribute if anything gets in my way, and at least attach an example to this ticket. Thanks.
Thanks. I'm attempting to upgrade to loopback-boot 2.0 but this is a blocker for me.
I am afraid this issue is not a priority for us at the moment, thus I won't have time to implement it anytime soon. Can you contribute the implementation yourself?
—
Reply to this email directly or view it on GitHub #49 (comment).
Activity
STRML commentedon Nov 13, 2014
Thanks. I'm attempting to upgrade to loopback-boot 2.0 but this is a blocker for me. My use case is essentially model schema discovery from a custom (unsupported) database. In 1.0 I simply ran a function that modified the JSON configuration before passing to loopback-boot. I am thinking of simply implementing
dataSource.discoverSchemafor this custom connector - do you have any examples of that data that being merged into the models passed to loopback-boot?bajtos commentedon Nov 13, 2014
My knowledge of schema discovery is very limited, @raymondfeng knows much more. I believe the result of
dataSource.discoverySchemais mostly the same as the content ofcommon/models/model-name.json.bajtos commentedon Nov 13, 2014
I am afraid this issue is not a priority for us at the moment, thus I won't have time to implement it anytime soon. Can you contribute the implementation yourself?
STRML commentedon Nov 13, 2014
I’m going to see what I can do with discovery - from there I’ll contribute if anything gets in my way, and at least attach an example to this ticket. Thanks.
shlomiassaf commentedon Feb 21, 2015
@bajtos,
I sent PR for this enhancement, #96
Could you please check?
Thanks.