We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 91c25b8 commit f24cfa2Copy full SHA for f24cfa2
_faq/contrib/jsdoc.md
@@ -0,0 +1,13 @@
1
+---
2
+question: When should I write JSDoc comments? When shouldn't I?
3
4
+
5
+JSDoc comments (the ones that start with `/**`) should be used for everything
6
+that's part of the public interface. They should not be used for anything else.
7
8
+The API reference documentation on this website is automatically generated from
9
+JSDoc comments. So adding a JSDoc comment to something has the effect of making
10
+it part of the documented public API. Do not add JSDoc comments to internal
11
+interfaces. If you want, you can write a comment that looks like JSDoc but
12
+doesn't start with `/**`. But it's usually better to use plain English since
13
+those comments don't need to be machine-readable.
0 commit comments