-
-
Notifications
You must be signed in to change notification settings - Fork 868
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
Messenger component does not work with PUT, DELETE, GET #3082
Comments
The fact is that |
@soyuka Hi! Thank you for your response. I agree with you at some point about GET operations, but what about DELETE. DELETE is a mutator and in my opinion, should work in the same way as other mutators (POST or PUT). |
It would allow to access the whole context (including the HTTP verb used), and I'm sure that it will be useful to many! |
Isn't yet fixed see #3157 (comment) |
* Issue api-platform#3082: Add and use ContextStamp. * Issue api-platform#3082: Add tests. * Issue api-platform#3157: Correct passing of context. * Issue api-platform#3157: Minor corrections.
* Issue api-platform#3082: Add and use ContextStamp. * Issue api-platform#3082: Add tests. * Issue api-platform#3157: Correct passing of context. * Issue api-platform#3157: Minor corrections.
Is this still an issue. I'm likely to want to use this use case imminently in my project. Happy to work on a PR if need be, if someone can advise on what is still outstanding on this. The comments on #3157 (comment) don't make it clear what's still required on this and it's over a year old, so I guess a lot has changed since this was last discussed. |
Hello everyone! Symfony Messenger still doesn't support the ability to implement what the author wanted? I have a similar problem: Symfony 5.2 with api-platform 2.5: // src/Entity/User.php
// src/MessageHandler/CommandHandlerInterface.php
// config.servises.yaml
// src/Message/Command/CreateUserCommand.php
// src/MessageHandler/Command/CreateUserCommand.php
CreateUserCommand - OK I want to implement an update: // src/Message/Command/UpdateUserCommand.php
// src/MessageHandler/Command/UpdateUserCommand.php
Unfortunately, I could not find a solution to this problem in open sources. Perhaps someone faced a similar task? @mxkh, did you manage to find answers to your questions? Thanks! |
I know this is quite old and I'll make a new issue regarding that but @entermix in case you (or someone else) are still looking: |
Hi! I want to use Message component with PUT\PATCH, DELETE and GET but as I understand the message component work only with POST method, am I right? For example
In this case, I expect that all input DTO's (commands\queries) will be passed to their handlers as in POST case. Is it possible to do without custom code? How do you see it's better to use message component for other request methods e.g. GET, PUT, DELETE to implement CQS or CQRS?
The text was updated successfully, but these errors were encountered: