Global schema options
See original GitHub issueIt would be nice to be able to return schema options that will be applied to all models from the .forRoot call.
For example, If I want timestamps on all of my models I have to pass {timestamps: true} to all of my models. It would be nice If i could just return something like this from .forRoot Options and spread it into each model when calling .forFeature
{
uri: "myUri",
schemaOptions: {
timestamps: true
}
}
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Mongoose v6.8.1: Schemas
Schemas have a few configurable options which can be passed to the constructor or to the set method: new Schema({..}, options); // or...
Read more >Mongoose: How to make the global schema settings working ...
This document introduces a way to register global schema settings by registering global plugins, but it does not mention the situation when ...
Read more >Global Schema - HULFT
Global Schema can be uniformly managed with "Global Schema settings" in the control panel. In "Global Schema settings", youb can view, delete, and...
Read more >Settings - Shopify.dev
The settings_schema.json file controls the content of the Theme settings area of the theme editor. Settings in this file translate to global theme...
Read more >Global Schema | r e a l - p r o g r a m m e r - WordPress.com
A local schema is a schema for a single document. Every document can have its own schema. It is possible that several documents...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
global options are added in 6.1.0-6
@kpfromer this can be closed, when you want to
no, i did not use nest & type-graphql yet, but it is a planned feature