-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[No QA] Improve guidance for JSDocs #7177
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
NAB: Might be easier to read if the Do Nots and the Dos are grouped together
Ah good call. I created some separation between them and listed the "dos" before the "donts". |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @marcaaron in version: 1.1.29-6 🚀
|
🚀 Deployed to production by @roryabraham in version: 1.1.30-3 🚀
|
Details
There are some pretty inconsistent usages of JSDocs happening in the codebase. I tried to write them down here so they are easier to enforce in general. Many of these rules are things that we are implicitly asking for and on an inconsistent basis. There is no way to know we want them done this way so nobody can be expected to do it.
Fixed Issues
❌
Tests
❌