refactor: set all inverse edges to allow multiple parents #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the unique option from all inverse/from edges, meaning a child entity may now always belong to potentially multiple owners/parents. This is to allow proto messages in the database to be reused if the wire-format bytes of the message are identical.
Depends on #63
Note
Only the following files are manually modified; the rest are auto-generated
backends/ent/*.go
internal/backends/ent/schema/*.go
Miscellaneous
DocumentMixin
, more duplicated code but better clarityMetadata
-->SourceData
edge/cc @ashearin @lmphil @pkwiatkowski1 @Strakeln @jmayer-lm @EphraimEM