Configurable serialization for generate POJO #186
Conversation
With POJOs being serilizable and having a serialVerionId field, everytime code generation happens - while developing and iterating on the spec, the diff include the unchanged files due to the serialVerionID change. Hence the config.
|
Hi @rahulkavale and thanks for the PR. Can you just explain what kind of issues you had with POJOs that implement serializable interface? |
|
@stojsavljevic One of the major issues was since the POJOs are marked as the serializable and have a serialVersionID field, every time code is generated, it produces a very large changeset as every POJO now has a new value for serialVersionID field. This is causing noise in the corresponding commit for the generated code. Hence the change. |
|
Generated code should not be version controlled. In the future, can you please create an issue first. |
|
@stojsavljevic Cool, I had already made these changes for my usage and wanted to submit it back to community. Thanks for the feedback. |
|
Related #264 |
Add configuration to make POJO not implement serializable.
The default value for the configuration is kept to true so that existing behaviour to make POJO serializable continues to behave as expected.