Improve Behavior documentation #2365
Merged
Conversation
This file contains hidden or 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
Two main goals 1. Make it clear that View life cycle functions are available on Behaviors 2. Improve grammar/consistency of docs when referencing Views and Behaviors Specifically the docs had alternated between `behavior`, `view`, Behavior, View, and behavior, view to refer to Behaviors and Views. In addition to some spelling/grammar stuff, I attempted to fix this by following the convention that: `View` and `Behavior` refer to the Marionette.View and Marionette.Behavior classes View and Behavior refer to a View or Behavior class (possibly a subclass of `View` or `Behavior`) view and behavior refer to instances of a View or Behavior class.
jasonLaster
added a commit
that referenced
this pull request
Feb 24, 2015
Improve Behavior documentation
|
Great! Great! Improvements |
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.
Two main goals
Behaviors
Behaviors
Specifically the docs had alternated between
behavior,view, Behavior, View, and behavior, viewto refer to Behaviors and Views.
In addition to some spelling/grammar stuff, I attempted to fix this by following the convention that:
ViewandBehaviorrefer to the Marionette.View and Marionette.Behavior classesVieworBehavior)