Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Janos Szurovecz
    @szjani
    If you have any questions feel free to ask.
    Janos Szurovecz
    @szjani
    What would you like to see in predaddy 2.0?
    Janos Szurovecz
    @szjani
    I have just released 2.0.0-RC2
    Even closer to the final release :)
    Janos Szurovecz
    @szjani
    2.0.0 is available \o/
    Janos Szurovecz
    @szjani
    What do you miss from predaddy? I have started to work on version 2.1
    Janos Szurovecz
    @szjani
    DoctrineAggregateRootRepository has been already added which can be used as a base class in CQRS applications
    Janos Szurovecz
    @szjani
    Considering to implement an upcasting feature to ease replaying refactored events. http://www.axonframework.org/docs/2.1/repositories-and-event-stores.html#event-upcasting
    Janos Szurovecz
    @szjani
    I'm going to check whether giving priority for handlers can be implemented without any BC breaks
    Janos Szurovecz
    @szjani
    I think it can be implemented. If you're interested in it: szjani/predaddy#1
    Janos Szurovecz
    @szjani
    Handler prioritization is available on branch 2.1
    Janos Szurovecz
    @szjani
    predaddy 2.1.0 has just been released
    Janos Szurovecz
    @szjani
    predaddy 2.2.0 is available. The changelog can be found here: https://github.com/szjani/predaddy#22
    Janos Szurovecz
    @szjani
    Version 3.0 is under development, final release later. Waiting for feature requests.
    Janos Szurovecz
    @szjani
    Janos Szurovecz
    @szjani
    Message validation based on Symfony Validator components: https://github.com/szjani/predaddy-symfony-validator
    Janos Szurovecz
    @szjani
    Predaddy 3.0 RC1 is available. I don't plan to change anything except the documentation from now.
    Janos Szurovecz
    @szjani

    A better, bank account example is available for both CQRS and ES approaches.
    https://github.com/szjani/predaddy/tree/3.0/src/predaddy/domain#cqrs
    https://github.com/szjani/predaddy/tree/3.0/src/predaddy/domain#event-sourcing

    I plan to release 3.0 these days, so if any of you have any issues with predaddy, let me know that.

    Janos Szurovecz
    @szjani
    Okay, hopefully the last feature for predaddy 3.0: message propagation can be stopped. It's a really small change, but maybe a usefull feature for some predaddy users.
    szjani/predaddy@9d2cb78
    This message was deleted
    Janos Szurovecz
    @szjani
    I proudly announce that I've just released predaddy 3.0. http://goo.gl/HQ1STI
    Piotr KacaƂa
    @telemetrik
    GJ mate :) A very vital addition to PHP community!
    Josh Taylor
    @joshuataylor
    What is everyones opinion on the symfony serializer? It is starting to look really good. http://symfony.com/doc/current/components/serializer.html
    Josh Taylor
    @joshuataylor
    does predaddy-doctrine-orm not flush() entities? it persists, but doesn't flush
    where does that responsibility lie?
    Janos Szurovecz
    @szjani
    Sorry, I did not follow this channel. It was quite a long time ago you asked @joshuataylor , but let me answer your question.
    You can use WrapInTransactionInterceptor with the doctrine implementation of TransactionManager. It flushes and commits the already opened transaction after the handler has been invoked.
    It can be found here: https://github.com/szjani/trf4php-doctrine
    The reason behind this is that you may want to persist multiple entities at the same transaction, therefore it has to be handled on higher level.