Allow to create derivation in different projects #443
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.
Until now, used and created entities were required to belong to the same project.
With this PR we allow to create new derivations from any readable entity (used) to a writable entity (generated).
Even when the parent (used) is private, the child (generated) can be either public or private.
Tests are added to test all the possible combinations.
Other related changes:
/hierarchyendpoint needed a fix to consider the case where a public generated entity G is derived from a private used entity U, and the user cannot read the private used entity U because it's in a different project. In that case, the public generated entity G should be returned as a root node, independently from the derivation type.derived-fromendpoint needed a fix to ensure that the specified generated entity is readable.Fix #427