I previously opend a feature request for a modifiable state within a selector (#1679), because i have a problem with the recalculation / slicing / preprocessing of the state, every time >100mb. Now i have read that you plan that the state is only recalculated if the output changes for v4 (not the parameters, https://www.ngxs.io/concepts/select#joining-selectors )[would also exactly solve my recalc

Currently, you are not able to use middleware per handler in "clean way" (you can still manually wrap the handler function, or have separated router).

It would be nice to be able to add middleware per handler.

As a good reference point, you can use chi router: https://github.com/go-chi/chi

• the code never changes there
• costs integration work (testing with several rails versions)
• it doesn't make sense outside of rails (usage of rails generator)

I would like to review the docs and explain also de concepts behind some decisions.
Things needed to explain:

• DDD objectives and reasons why.
• Core concepts like
  • bounded context
  • anti corruption layer
  • domain
  • value objects VS entities
  • aggregates
  • aggregate root
  • layered architecture and each one responsibility
  • reasons for the command and query bus
  • the even