-
Notifications
You must be signed in to change notification settings - Fork 50
ResourceEvent should be optional in query filters and providers #280
Comments
@jguittard Can you show example when the event is not available in |
I think he meant if you call |
Oh, yeah, this is what he meant probably :) Thanks @gsomoza. I misunderstood. Sorry @jguittard :) I have a lot of concerns about PR #281 and it seems to be also BC Break. I'm afraid that the library doesn't support RPC endpoints at all right now. There is something in codebase already ( Of course it will be nice to resolve also this issue somehow, to allow usage @jguittard @gsomoza thoughts? |
This repository has been closed and moved to laminas-api-tools/api-tools-doctrine; a new issue has been opened at laminas-api-tools/api-tools-doctrine#7. |
As a concrete example, let's say an entity has to be created from an RPC controller. A
DoctrineResource::create
method is then called. Thus, when calling it,data
is filtered through aZF\Apigility\Doctrine\Server\Query\CreateFilter\DefaultCreateFilter
(by default, should no extra configuration provided) as shown hereDefaultCreateFilter
), the event is not used at all.DoctrineResource::create
implementation, the event may not be available.The text was updated successfully, but these errors were encountered: