✨ Compile WP args schema from #[Param] attribute on handler parameters#40
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.
Summary
Add
#[Param]attribute on handler parameters so the args schema is compiled into WordPress'sregister_rest_routeinstead of being re-implemented inside every handler. WordPress now enforcesrequired/type/enum/sanitize_callbackbefore the handler runs, and the auto-discovery endpoint (/wp-json/<ns>) describes the route arguments.Why
RouteLoader::buildRouteArgs()was always emitting'args' => [], so:Usage
Compiled into:
Type inference (when Param::$type is null)
Backward compatibility
Handlers without
#[Param]keep registering with empty args — nothing else changes.