We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
2 parents 88ac4cf + 880152d commit 1a7df23Copy full SHA for 1a7df23
docs/writing-a-plugin/guidelines.md
@@ -28,6 +28,8 @@
28
1. Prefix any errors with the name of your plugin
29
- For example: `gulp-replace: Cannot do regexp replace on a stream`
30
- Use gulp-util's [PluginError](https://github.com/gulpjs/gulp-util#new-pluginerrorpluginname-message-options) class to make this easy
31
+1. Name your plugin appropriately: it should begin "gulp-" if it is a gulp plugin
32
+ - If it is not a gulp plugin, it should not begin "gulp-"
33
1. The type of `file.contents` should always be the same going out as it was when it came in
34
- If file.contents is null (non-read) just ignore the file and pass it along
35
- If file.contents is a Stream and you don't support that just emit an error
0 commit comments