Additional ways of defining model relationships #120
Merged
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.
So far,
propertyClass
property ofAttribute
,HeaderAttribute
, andHasOne
decorators accepted classes only. This pull request introduces a new way of defining relationships by provided string identificators.In order to use model's string identificator, the said identificator must be set on the model (
modelType
property), and the model must be provided in the list of models present in the DatastoreService (modelTypes
property).Why would you need to use string identificator instead of the exact class?
In case when two models have references between each other, the reference on one of the sides must be defined via string identificators to break the circular dependency.
https://github.com/infinum/ngx-hal/wiki/DefiningModelRelationships#circular-dependencies