Yes,
Inheritance and extension is not possible with Record and as it's only
for immutable data, it's can be tricky something.
Fully agree with the "AND" and not "OR" discussion :)
regards,
François
On 14/08/2024 17:22, Hans Van Akelyen wrote:
Great point Francois!
I do see benefit in using records where possible but those would only be useful for
"data" classes. Much of our metadata falls under this so it could and should be
investigated.
All other classes that still need the full power of extending and inheritance
can also still benefit from Lombok by removing boilerplate code.
So I think in this case it's more of an "AND" discussion and not an "OR"
Cheers,
Hans
On 14 Aug 2024 at 17:14 +0200, Francois Papon <francois.pa...@openobject.fr>,
wrote:
Ok, I understand, make sense :)
On 14/08/2024 16:55, Bart Maertens wrote:
I like what java Record would allow us to do and how much it could simplify
things.
We'd have to investigate what the impact on the code base would be before
we could start working on it, and implementing the required changes would
be a scary amount of work.
Personally, I'm not against the idea, but it won't happen any time soon.
On Wed, Aug 14, 2024 at 4:31 PM Francois Papon <francois.pa...@openobject.fr>
wrote:
Hi,
What about using java Record starting from java 21?
regards,
François
On 14/08/2024 14:51, Hans Van Akelyen wrote:
Hi All,
I would like to propose to add Project Lombok [1] to our project.
Lombok allows us to generate some boilerplate code on the fly feel free
to take a look at the feature list [2].
This will allow us to focus on the code without having to worry about
getters/setters and their naming convention.
It seamlessly integrates with IntelliJ and is MIT licensed.
Quote from the project:
Lombok is a Java library that provides annotations to simplify Java
development by automating the generation of boilerplate code. Key features
include automatic generation of getters, setters, equals, hashCode, and
toString methods, as well as a facility for automatic resource management.
It aims to reduce the amount of manual coding, thereby streamlining the
codebase and reducing potential for errors.
Cheers,
Hans
[1] https://projectlombok.org/
[2] https://projectlombok.org/features/
