Add Lombok to reduce boilerplate code and add a builder pattern about sql-to-jdl HOT 3 OPEN

Not much real value in Lombok, I have used it, it has good things but the reality is it does not provide that much added value, this is a small project.
And for big projects, I would definitely not go for Lombok.

I am not against it, just to say this is small project, not much gain from adding Lombok, it adds complexity.

from sql-to-jdl.

Agreed that it adds complexity, but it can do some really cool things with minimal code. Personally, I have never run into any problems. If problems arose, delombok could be used and the boiler plate code merged back in manually.

This is not a priority. However, if you would accept a PR then I would likely see what I could come up with.

I wanted to do more tests like src/test/java/org/blackdread/sqltojava/test/general/MustacheTest.java, and a builder pattern would be a lot more readable.

from sql-to-jdl.

If a PR is made, I can agree to merge.
Project is small so not much impact; in other personal or work projects, none have Lombok.

from sql-to-jdl.