fix(persister): added condition to check if entity values are array #203
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.
I had the same issue here: #202
It was working well until I update the library.
Error context:
I defined the relationship datatype as array and not as Collection or ArrayCollection.
It seems that if you didn't specify the datatype as Collection or ArrayCollection, the library loads it as array, and after in inner checks It only checks if it's a Collection, otherwise threats it as a Object, so it throws a
TypeError
.What I did
I added a check if it is an array, and processed it like if it was a Collection.
For me it is working, hope it helps.