WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #26799, comment 5


Ignore:
Timestamp:
01/28/2014 09:42:52 PM (6 years ago)
Author:
gcorne
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26799, comment 5

    initial v1  
    11I understand your point of view and think that it would be worthwhile for someone to open a dialog with Jeremy or one of the other Backbone leads. Since version 1.1 has already been released, I think we shouldn't delay updating because the delay will mean that plugin authors writing new code may write in a style that is only compatible with older versions of Backbone. The good news is that if plugin authors are taking advantage of {{{wp.Backbone.View}}}, the change to no longer automatically attach {{{this.options}}} won't cause problems. We could consider adding wrappers for {{{Backbone.Model}}} and {{{Backbone.Collection}}} to provide us with a way to try and avoid backwards-compatibility issues, but that won't help Backbone code that has already been written.
    22
    3 We also could explore using {{{wp.Backbone = Backbone.noConflict()}}} so that it is easier for plugin authors to supply their own version of Backbone should they choose.
     3Another approach worth exploring is using {{{wp.Backbone = Backbone.noConflict()}}} so that it is easier for plugin authors to supply their own version of Backbone should they choose.