UnderlineNav2: Take the listing html structure back to its original state #3559
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.
When running integration tests at dotcom, found out that the select issue fix introduces some changes that was breaking
UnderlineNav
usages. (Error log (GitHub stuff only link))It is mainly the HTML re-structure I made here.
Relying on the implementation details on the consumer side for the
key
prop for iteration causing some issues. I was expectinglinkItem.props.children
to always have a value however for custom components like below, there is no children passed. So taking the HTML structure back to its origin where we don't need to manually extract the key value from the UnderlineNav children components, so that the iteration all will be on the consumer side.Closes # (type the issue number after # if applicable; otherwise remove this line)
Screenshots
Please provide before/after screenshots for any visual changes
Merge checklist
Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.