Phil Chen

I think `Commanded.Application.Config` might be a suitable place to store `aggregate_default_lifespan`, which allows applications to decide whether to set it at runtime or compile-time.

I think that these types of configurations are actually used by commanded applications only. I created a commit to demo the changes: https://github.com/fahchen/commanded/commit/7c1741f5de3d962d7d562b13e74dbfdc76a31881

I think this PR may not be a good approach. Firstly, each application has the responsibility for its own configuration, other applications should not depend on that.(official document states at...

Maybe we could divide these problems into two parts. One is to support the default lifespan for aggregates, another is to attempt to fix the time bomb, or alternatively, leave...

> I see that you're looking to configure a specific value and you're wondering at which level this could be done. Well, you have a few options, each offering different...

Thanks for your reply. My scenario is simpler than you now. Currently, I move `working_list` messages back to the `list` when my system is about going up manually. Maybe `Broadway.Producer.prepare_for_start/2`...

I am extremely grateful to @ejpcmac for providing this package, which has performed excellently in my projects. However, it lacked some features I needed, and it appeared that the repo...

That’s a good scenario. Maybe we should provide some common mutation functions.

@jonatanklosko Thanks for your reply. > what code is the smart cell supposed to generate? The smart cell consists of two parts: `data` and `options`, sso I thought the generated...