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.
Continuation of #10638. Field paths within the schema map are not correct.
For example, an unnamed tab containing a text field should have the schema path:
_index-0.fieldWithinUnnamedTab
However, within the schema map that path is formatted as:
fieldWithinUnnamedTab
The leading index in the first example should exist, as this field is nested within another field, regardless of this field being unnamed. Otherwise, it would be impossible to traverse the schema and lookup this field. This discrepancy does not present itself easily, though, because fields are also provided the wrong schema paths. They can properly locate their schema within the schema map because they match despite being incorrect.
Here's comprehensive example of how field paths should be formatted: