Docs: Add Developer Tools setup in Getting Started #19074
Merged
Conversation
This file contains 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
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.
Description
Adds a new section for Developer Tools for setting up an editor to the Getting Started page in the Contributors Handbook. The section recommends setting up EditorConfig and Prettier extensions.
This can precede the Prettier PR #18048 to help people get setup prior, wording will just need to be updated after that release to remove references to the PR in the doc.
How has this been tested?
Follow directions on documentation page, found on branch here
Types of changes
Developer docs.