Field API: update docs to better communicate field types #73349
Merged
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.
What?
This PR updates the
README.mdto provide better examples with field types.Why?
While the
typeprop was documented, it wasn't surfaced properly in the examples. As a result, LLMs and humans sometimes missed it existed.How?
All of the examples now use it the
type.Testing Instructions
README.mdand paste them into any LLM.The expectation is that, after these changes, the fields generated by the LLM consistently include the
typeproperty (while before it was a rare event).