make CollectionBinder optionally an AMD

[rweng]

I had trouble when optimizing my js code with requirejs, because CollectionBinder executed as soon as it was loaded, whereas ModelBinder was an AMD und thus not yet defined.

So I propose making CollectionBinder an AMD, too.

[DocLabyrinth]

I'm also encountering this problem when trying to make an optimised build which includes the two files. It's possible to concatenate them during the build process or wrap the collection binder manually, but additionally having the AMD define call in the collection binder would make life easier.

[raresvla]

+1

[jefftougas]

👍

[bharatpatil]

Wow!!! Thanks...!!!

[gaydenko]

While this bug fixing is still pending during almost a year, can anybody please explicitly explain how to workaround the issue with "Please include Backbone.ModelBinder.js before Backbone.CollectionBinder.js" exception?

[bharatpatil]

@gaydenko - If I correctly understood you, Copy and paste green lines from "File Changed" tab above in Backbone.ModelBinder.js (of course overright red lines).

[gaydenko]

I have tried - there was an error on requerjs building, but after removing ModelBinder from define array (I mean that patch) I have got built project at last (dependencies are defined in requirejs config file). Thanks!

[crebuh]

would be great if this could be integrated into the current release?

[cliren]

@theironcook did you get a chance to merge the amd support PR for collection binder?

[theironcook]

The latest (v1.0.6) has this feature.

[cliren]

great, thanks!