-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Parameters documentation improvements #2187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
core/filters.md
Outdated
parameters: [ | ||
'dummy' => new QueryParameter( | ||
provider: ReadLinkParameterProvider::class, | ||
extraProperties: ['resource_class' => Dummy::class] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it also showcase the extra property uri_template
?
core/filters.md
Outdated
private ?int $id = null; | ||
public function apply(QueryBuilder $queryBuilder, QueryNameGeneratorInterface $queryNameGenerator, string $resourceClass, ?Operation $operation = null, array $context = []): void | ||
{ | ||
$value = $context['parameter']?->getValue(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it advocate for $operation->getParameters()->get('myParameter')->getValue();
approach more than through the context?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really imo as the filter receives the parameter it is called on, in the other case you need to find the parameter though a filter may be used on many parameters.
No description provided.