Fix #305: presenting arrays of objects when the entity class isn't explicitly passed into present #307
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 wrote two failing specs and then refactored the code a little to make them pass. I tried to mirror the formatting as much as possible.
I had to manually create a named class in one place in order to properly create a failing test. Using
Object
wouldn't work because of the waypresent
walks up the ancestor tree.I also made an explicit choice to derive to auto-detect the entity from the first object in the collection because it was the simplest solution. It might make sense to expand it to auto-detect the entity of each object in the collection, in case someone returns a collection with different types of objects.