I think it would be interesting to address in a chapter of the documentation good practices both in programming and in the design of persistent classes.
It would be ideal to present some code examples.
Some examples to illustrate my point:
How to transform a data transfer Object (dynamic object) coming from a Rest API to create a persistent object?
How to implement design patterns (factory, facade, query-builder, etc.)?
In which case to favor the object approach of persistent classes over the SQL approach and vice versa.
Thank you for submitting the idea. The status has been changed to "Needs review".
Stay tuned!
