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.
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
feat(StructuredList): Accessibility refactor #8172
feat(StructuredList): Accessibility refactor #8172
Changes from 11 commits
6954ba0
cb09d20
1f46ed5
f655b31
156cbc1
bd86cea
909726a
fb68deb
48ef999
15310ad
fd90e92
5af34a2
0487407
606c728
c2184ea
2673889
7d835f4
c151da7
84fa755
2cdf113
08ce487
110e400
e6a9615
07eda0d
7770b66
12c3862
939bcfd
4d9c07c
182a935
1789d5d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Something I'm a little unsure about here is if they still pass in a
value
what should we do with it?One tricky thing with adding in context is that if, for whatever reason, someone uses
StructuredListInput
without the wrapper components then this component ends up not working because the context is never defined.I guess this kind of goes back to your point earlier about how this might be too big of a breaking change to safely migrate to in v10? Curious what your thoughts are
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.
its worth talking about for sure -- I guess what are the chances or what is the actual use case of only using StructuredListInput? Should we put a call out on Slack or maybe kick this whole can down the road to v11?
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.
@dakahn maybe the safest thing is just to wrap it all behind a flag, I guess? If we want to do it in v10, then I think we'll just need to make sure we understand what props teams could be supplying and how to leverage/use them, if so.
For example, if someone is using a
label
then they might be expecting in a test to be able to find a node using thatlabel
. If we no longer use it in the component, then their test would be break.