Lars Vonk

I can give it a try. I'd opt for failing when such a parameter is passed in, perhaps via a setting? Like `fail_on_undeclared_params = true|false` then when it is `false`...

Hi @namusyaka thanks for replying. The optional parameter is `baz` in the example, not `bar`. `'/foo/:bar/?:baz?'` (my apologies for the confusing names in the example). Both ways of defining an...

> Actually the patterns in the route and the filter are not necessarily closely related. This behavior is established. Hmm okay. I did not consider that. It still feels strange...

Hi @mattgibson, My thoughts: We comply to GDPR as follows: our application is tenant based. Whenever a tenant is deleted we delete all aggregates belonging to that tenant from the...

So if I understand you correctly you replace events in the event store with so called Tombstone events? Or do you just add such an event to the end of...

Ah thanks for clarifying. Perhaps we could/should add a section in the documentation on this topic on what possibilities you have in order to comply to GDPR: - Encryption -...

> > Brute force deletion > > Does this mean _Brute force deletion_ of events? Or data in projections? I have update the comments, I meant indeed Event Deletion.

Thanks for reporting. Will look into this coming days.

The `WorkflowHelpers` need to use the `FakeCommandService` and register it in the Sequent config. So we need to somehow detect which spec `WorkflowHelpers` and which needs the `CommandHandlerHelpers`. So we...

Yes that would be nice. Although I think we should solve the conflicting `WorkflowHelpers` and `CommandHandlerHelpers ` at the same time. We could have something like this (like in `EventHandlerHelpers`:...