updates plugin.views Reference.md entry to a clear and working example #1113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current example for setting plugin-specific views engines breaks because
require('jade')
returns an object (and so extends and invalidates the options that get passed topack.views
). It also does not clearly show that "jade" refers to the file extension and not the module itself:I'm proposing a simple change to the following, which tries to clarify that "html" refers to the file extension of the view template and also shows a working example that follows the guidelines specified in the docs: