magic-bean VS AssertJ

I like to use Magic Bean for this kind of stuff if I can't use records for some reason.

I recently stumbled upon https://github.com/bowbahdoe/magic-bean . This would be an example of solving developer needs - compatibly with the jdk way but currently ugly. Maybe we can make it nicer in the future somehow?

I think Hibernate / cases where real getters and setters are desired are the remaining usecase. The code generator I published however long ago handles specifically that boilerplate, but its Java 17+ only. https://github.com/bowbahdoe/magic-bean

For those anemic models, when they are called for (JPA) - https://github.com/bowbahdoe/magic-bean

And if you want non-magic getters and setters there is this: https://github.com/bowbahdoe/magic-bean

Maybe not the feedback you want, but would you consider developing something that looks like plain old (and frankly beautiful) AssertJ?

AssertJ - fluent assertions

AssertJ https://github.com/assertj/assertj

Truth or AssertJ for easier assertions in tests with better exceptions

While we are at it: AssertJ is very powerful for writing assertions.

In OO you can make beautiful DSLs that allow really declarative use within that domain, e.g. test assertions in AssertJ, but everybody in the OO world is sensible enough to not try and claim OO as such being declarative. I guess they don't feel a need to try to prove the superiority of the paradigm.

AssertJ comes with a variety of assertions that can be chained together and are specific to the type of your "actual" variable.

At any rate it comes from a library called assertj.

While Hamcrest add some fluentidity to unit tests ä, I prefer the fluent assertions of AssertJ.