Clarify why a TreeView should not be used for navigation #478
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
ericwbailey
temporarily deployed
to
github-pages
GitHub Actions
Inactive
ericwbailey
changed the title
mperrotti
approved these changes
Apr 26, 2023
joshblack
reviewed
Apr 26, 2023
Co-authored-by: Josh Black <joshblack@github.com>
|
@mperrotti I just pushed up a note about it, if you don't mind giving that a second review. |
mperrotti
approved these changes
May 9, 2023
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.
This PR addresses a request in Slack by @howdyray. It adds a paragraph to explain usability expectations for the TreeView component, and how there may be a mismatch in expectation if used for static navigation.