You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Eclipse JNoSQL Lite, which currently requires entities to have a default non-argument constructor and supports Java bean standards for object mapping, is looking to expand its functionality to include support for Java Records and the Builder Pattern. This enhancement aims to facilitate the use of immutable entities and improve the creation of complex entities, making the framework more adaptable to modern Java practices.
Feature proposal
Developers need a way to create persistent entities that are defined as records. This would give them a more robust, type-safe, and concise data model method. Additionally, integrating builder pattern support would make it easier for developers to construct entity instances flexibly and straightforwardly. This update would require necessary adjustments in the framework's entity processing mechanics to accommodate these features and would be complemented by updated documentation and examples demonstrating the new capabilities.
The text was updated successfully, but these errors were encountered:
Which JNoSQL project the issue refers to?
JNoSQL Extensions
Use case
Eclipse JNoSQL Lite, which currently requires entities to have a default non-argument constructor and supports Java bean standards for object mapping, is looking to expand its functionality to include support for Java Records and the Builder Pattern. This enhancement aims to facilitate the use of immutable entities and improve the creation of complex entities, making the framework more adaptable to modern Java practices.
Feature proposal
Developers need a way to create persistent entities that are defined as records. This would give them a more robust, type-safe, and concise data model method. Additionally, integrating builder pattern support would make it easier for developers to construct entity instances flexibly and straightforwardly. This update would require necessary adjustments in the framework's entity processing mechanics to accommodate these features and would be complemented by updated documentation and examples demonstrating the new capabilities.
The text was updated successfully, but these errors were encountered: