Repository navigation
[6.x] Add fieldtype inspection commands - #15737
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Expose the installed fieldtype registry and configuration definitions through two read-only commands, so agents and developers can inspect valid settings without reading individual PHP classes or maintaining a separate schema.
The output includes the Statamic version, registered fieldtype metadata, configuration defaults/options/conditions, and shared field options. It respects add-on registrations and appended configuration. Configuration controls use
editor_type; opaque PHP values and JavaScript-provided toolbar choices are marked unresolved rather than guessed. Without--json, the commands produce a table or YAML. Unknown handles return a failure exit code and a JSON error when requested.Validation: 14 focused tests / 195 assertions pass, covering every registered core fieldtype, add-on configuration, aliases, unresolved values, errors, and Artisan/Please discovery. Laravel Pint passes for all five changed PHP files.