fix(ui) Fix tags and terms columns on nested schema fields #7782
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 we updated ant design, I believe they introduced a new bug where the
rowIndex
for nested table rows is inconsistent depending on the method you're using. TheonCell
function gives the overall index as if it were a flat list of rows while therender
method gives the index of the row in the nested field context (this is not how it used to work).Therefore, the
tagHoveredIndex
piece of state would never line up with the row and it would never think you're hovering over it so we would never show the option to add tags and terms. SincefieldPath
is unique in a schema anyways, we don't need therowIndex
here so I simply remove it.Checklist