Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider when to emit database IDs in serialisations #30

Open
pahjbo opened this issue Dec 5, 2023 · 1 comment
Open

Consider when to emit database IDs in serialisations #30

pahjbo opened this issue Dec 5, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@pahjbo
Copy link
Member

pahjbo commented Dec 5, 2023

In general if an entity is a composition then in a full export of a model, then no database ID is required as the object can only appear as a "child" of the parent - however, in the case of serialising in a API then it is more likely that an efficient API design can
only be achieved if the database ID is emitted.

It would be good to be able to make the serialisation "switchable" between these two scenarios.

@pahjbo
Copy link
Member Author

pahjbo commented Oct 28, 2024

could use @jsonfilter and different object mapper setups

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant