Update backbone to 1.2.x and consider new "update" collection event

[darky]

No description provided.

[magalhas]

I can do this but meanwhile feel free to open a PR for it, it looks like pretty straightforward changes 👍 Thank you for opening the issue

[darky]

Close this, because this kill backbone <1.2.0 compatibility

[magalhas]

@Darrrk can you please elaborate why does the compatibility breaks? I'm going to reopen the issue for the sake of this discussion. Thank you!

[darky]

Since backbone 1.2.0 you can use update event instead add and remove
Pros:
We can use only one update event instead any amount of multiple add or/and remove events.
Negative:
Breaks compatibility with backbone less than 1.2.0

[magalhas]

I don't see why this change couldn't be included in the incoming version of this lib. React also includes some breaking changes in some versions and we'll keep up with it, I guess the same approach applies do Backbone. If the dev needs, simply lock backbone-react-component to the minor version (0.8 in this case).

Do you agree?

Cumprimentos,
José Magalhães

On Fri, Jul 3, 2015 at 11:18 AM, Vladislav Botvin
notifications@github.com wrote:

Since backbone 1.2.0 you can use update event instead add and remove
Pros:
We can use only one update event instead any amount of multiple add or/and remove events.
Negative:

Breaks compatibility with backbone less than 1.2.0

Reply to this email directly or view it on GitHub:
#82 (comment)

[darky]

Ok, giving PR

[magalhas]

Sweet 👍

[darky]

#85 merged