Skip to content

Conversation

manojswn94
Copy link

@manojswn94 manojswn94 commented Aug 4, 2025

Fix #29835

ISSUE :
Entities generated with DTO mappings have included @JsonIgnoreProperties for SQL databases,
and it can lead to unexpected serialization behavior.

SOLUTION :
This change ensures that @JsonIgnoreProperties is only added to entities when:

  • Not using DTO mapping

  • Using NoSQL databases (like MongoDB or Cassandra)

  • Entities using DTOs rely on MapStruct for transformation, so @JsonIgnoreProperties is unnecessary

  • For SQL databases, this prevents unnecessary annotations and results in cleaner entity generation

…oreProperties

entities generated with dto mapping should not include @JsonIgnoreProperties for sql databases,
as it can lead to unexpected serialization behavior. this change ensures that @JsonIgnoreProperties
is only added to entities when not using dto mapping & for nosql (like mongodb, cassandra)

Fix jhipster#29835
@manojswn94
Copy link
Author

manojswn94 commented Aug 5, 2025

Hi maintainers,

Workflow Job Log (ref: 47359660799)

CI is failing for this PR due to errors (dependency convergence, disk space, Chrome crashes, etc.) that are also seen in other recent PRs ([#30254], [#30234], [#30223]). These issues seem to be related to the CI environment and not my changes.

Could you please review the code logic in this PR and, if possible, check the underlying CI issue, or let me know what would be the best thing for me to follow
@mshima @DanielFran

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Entity generated with a mapping using a dto should not have a @JsonIgnoreProperties
1 participant