Evil tool for prooph when you want to temporary hide your synchronous CQRS backend behind request/response interface to use in legacy REST or WebApp controllers.
Open Issues: 1
- php: ^7.1
- prooph/event-sourcing: ^5.2
- prooph/service-bus: ^6.1
- psr/container: ^1.0
- psr/log: ^1.0
- phpstan/phpstan: ^0.8.5
- phpunit/phpunit: ^6.2
This package is not auto-updated.
Last update: 2023-06-03 10:21:05 UTC
This is "evil" tool for prooph toolbox.
Why bother then?
If you want to release minimum viable product and you dont want to deal with asynchronous stuff on frontend, like optimistic UI and error handling, because you do not care your commands are processed synchronously, you can hide your synchronous CQRS backend behind request/response interface.
Then you can have nice "proophful backend", well ready to make it asynchronous, but use it with simple or legacy request/response REST or WebApp controllers for frontend. Using this is considered as bad practice, because you loose all good thing prooph can offer to frontend.
But you can use this and when you prove your business concept is good, you can make your frontend shiny and asynchronousful.
1) Install this library through composer
composer require tomcizek/prooph-response-recorder
Please feel free to fork and extend existing or add new features and send a pull request with your changes! To establish a consistent code quality, please provide unit tests for all your changes and may adapt the documentation.