Fixes #91: Add Backbone.RelationalModel.setup method to set up reverse relations etc. when not using .extend. (CoffeeScript!)
#112
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Backbone.RelationalModel.extend options: partOfSupermodel: `true` if this model should use the same model collection and relations as its superclass. submodelTypeAttribute: attribute that should be checked to determine the type of object to build when attributes are passed in. Default: `type` submodelType: value of attribute defined using submodelTypeAttribute that will cause this type of object to be built.
…d `submodelTypeAttribute` properties.
…nal into new-submodels
…ly to set up a Backbone.RelationalModel subclass after defining one without using .extend().
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #91.
Note that this pull requests depends on #111, as I've based the
.setup()method on that revision. I'll probably have to reset the commits linked to this pull request once you've pulled #111 in, so we don't pull in all commits related to that request twice.