Add two new core methods to allow invoking possibly unknown methods on objects if they exist #1044
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.
Rationale:
This is such a common idiom throughout Ember and my Ember apps:
...that I think it makes perfect sense to solidify the paradigm in Ember, especially when the code is less than 10 lines long total. Great code exposing good patterns in small chunks feels like the new thing Ember is trying to achieve. For instance:
Ember.Evented
.I ask for naming suggestions as I don't particularly like
tryToPerform
.Two possible alternatives already suggested include:
methodExists
/invokeIfExists
canInvoke
/tryInvoke