fix(ui): self managed field paths #12290
Draft
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.
Fixes #12286. Self managed fields, i.e. custom fields that define their own path as a prop, consume their parent's path instead of the path that was given to them.
This was introduced in #11973 where we began passing a new
potentiallyStalePath
arg to theuseField
hook that takes the path from context as priority. This change was necessary in order to fix stale paths during row manipulation while the server is processing.This change, however, made it so that custom fields could no longer control their own path.
The fix is to lift the
potentiallyStalePath
logic out of Payload's default fields and pass it as a direct prop. This way thepath
prop is still available for direct use.