You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: