Use absolute paths when building entry classes #24
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.
When using nested expands, inline entries can contain deeply nested
properties and inline elements of their own. Rather than performing a
match on any node under the current, select only the first level
properties or inline entries nodes.
The bug I was having is this (arbitrary example):
products.Categories
would contain both Category and Section classes, since it was matching every nested entry rather than just the first level for each Product entry node. Also, properties were not being set on the first expand associations - soproducts.first.categories.first.ID
would be nil, even though the properties element was present for that category.