Disabling/Skipping plugins

[govindrai]

Do you want to request a feature or report a bug?
Feature Request

What is the current behavior?
Is there a way to disable a plugin for a specific model? I've enabled timestamps and toObject transforms for all my schemas using a plugin. Unfortunately, my subdocument schemas also end up using that plugin, I do not want my subdocs to have timestamps or be transformed. Is there a way to turn off a plugin for a specific schema? I know you can opt-in by assigning the plugin to each model, but is there an opt-out option?

Super naive first thought:
Maybe something like schema.prototype.skipPlugin(_nameOfPlugin_). Of course this would require plugins to be named, which could be useful..

Please mention your node.js, mongoose and MongoDB version.
All latest versions as of 12/27/2018

[govindrai]

Was able to achieve this by adding a custom skipCustomPlugin: true key/value pair to my schema's options. Then, in my plugin, I just check this property's existence and return from the plugin if it's set to true.

I was able to do this since I wrote the plugin, but it wouldn't be possible if I was using a third party plugin. It would be nice if there was a way to turn off any plugin.

[vkarpov15]

No way to do this right now. How about we add an option for disabling global plugins on child schemas? Naming plugins is a more complex change unfortunately.

[govindrai]

I think that is a good change, as I think most users would want plugins to work on their overall schema and not child schemas. And if they did want it to work on child schema, they could still use Schema.plugin() to enable it on those child schemas.

---

I also agree with "naming plugins" being a complex change. Either mongoose has to set a standard for plugin developers to put in an escape hatch (potentially by including a simple line of code like I did in my case), or some more robust functionality. Even something as simple as mandating that plugins be named functions could work too. For example,

module.exports = function myCustomPlugin(schema, options) {...}
module.exports.name === "myCustomPlugin"// true
Then there could be a function like schema.skipPlugins(['plugin1', 'plugin2']) that loops through all plugins and if it finds the name(s) of plugins to be skipped, it skips them.

There's probably more complexity to it, I'm sure, but just another thought.

[vkarpov15]

We already have an option to opt in to applying plugins to discriminator schemas, so a applyPluginsToChildSchemas wouldn't be crazy