-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
ref(js): Cleanup notification/utils.tsx #28679
ref(js): Cleanup notification/utils.tsx #28679
Conversation
- Move documentation comments above the function so LSP correctly picks up on them - Reduce some nesting with guard statements
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.
Oops it looks like we we've been doing python style docstring this whole time 😬
@@ -385,8 +384,6 @@ export const getParentField = ( | |||
parentId: string | |||
) => NotificationSettingsObject | |||
): FieldObject => { | |||
/** Render each parent and add a default option to the the field choices. */ |
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.
Can we auto format this?
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.
What are you thinking?
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.
idk if there's a lint rule for it
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.
Like no comments like /** ... */
?
Or also auto wrapping?
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.
Comment style
Move documentation comments above the function so LSP correctly picks
up on them
Reduce some nesting with guard statements