Let the user add a defaultConfig object when initializing the plugin. This object is then used to populate the config parameter of all the routes generated.
This is useful for example to tag all the routes generated by this plugin.
Let the user add a defaultConfig object when initializing the plugin. This object is then used to populate the config parameter of all the routes generated.
This is useful for example to tag all the routes generated by this plugin.
Do you think we'd better use _.defaultsDeep instead of _.defaults, that way the user won't replace validation rules by adding general rules.
For example:
defaultConfig:{validate:{params:Joi.array()}}
Hey! Thank you, seems like a good idea. :+1:
Do you think we'd better use `_.defaultsDeep` instead of `_.defaults`, that way the user won't replace validation rules by adding general rules.
For example:
``` javascript
defaultConfig: {
validate: {
params: Joi.array()
}
}
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Let the user add a defaultConfig object when initializing the plugin. This object is then used to populate the config parameter of all the routes generated.
This is useful for example to tag all the routes generated by this plugin.
Hey! Thank you, seems like a good idea. 👍
Do you think we'd better use
_.defaultsDeepinstead of_.defaults, that way the user won't replace validation rules by adding general rules.For example:
Hi @mdibaiee.
Looks nice, I am not used to work with lodash and I thought that was the default behaviour. 😄
@Istar-Eldritch Thank you! 😀
Published
hapi-sequelize-crud@2.0.11. ✋Thanks, I'm thinking on adding more stuff. But as is going to be more hardcore I'll create first issues to discuss it. 😉
Cheers
@Istar-Eldritch Great! I'm actively maintaining this repository, so no worries at all! ✌️