Add JavaScript naming conventions to frontend documentation#9448
Merged
Conversation
changelog: Internal, Documentation, Add JavaScript naming conventions to frontend documentation
mitchellhenke
approved these changes
Oct 25, 2023
Since they're typically defined as functions
matthinz
approved these changes
Oct 25, 2023
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
🛠 Summary of changes
Adds a new section "Naming Conventions" to the JavaScript guidance found in the frontend documentation.
This should match reality, so hopefully nothing here is controversial, but open to feedback all the same, or gaps if I missed anything.
Reference discussion: #9433 (comment)
📜 Testing Plan
See preview: https://github.com/18F/identity-idp/blob/javascript-naming-conventions/docs/frontend.md#naming-conventions