Supports subclassing Entities to an arbitrary depth, and on relationship entities #52
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.
nb: first of all, apologies for the white-space deletions, my IDE cleaned them up. I can resubmit without, if that's much easier.
I extended the extent to which MMRecord detects and uses Entity subclasses ( i.e. when it queries
shouldUseSubEntityRecordClassToRepresentData
). It now supports beyond a single level of subclassing (i.e. it checks recursively), and also allows relationship entities to be matched to a subclass as well, as in this example:A: it will now support Account subclassing for the following example:
Feedback is very welcome