fix(ujs) always handle native events, _also_ handle turbolinks if appropriate

[rmosolgo]

As mentioned in #108 , sometimes a turbolinks app still has native events. So,

• always handle native events
• also support turbolinks events

Since the UJS functions are public now, we could put turbolinks UJS in its own file, right? Using turbolinks would be:

//= require react_ujs
//= require react_turbolinks_ujs // or something

That's a backwards incompatibility though, maybe we should wait a bit

[xionon]

That's a backwards incompatibility though, maybe we should wait a bit

I don't know if it would divide well along this line, but maybe you could have react_native_ujs and react_turbolinks_ujs, and have react_ujs just be a manifest that includes both?

[rmosolgo]

oh @xionon good call, that would be a nice way of splitting it. I may try it in a later PR.

[rmosolgo]

just realized this could result in an unexpected double-mount on first page load, thinking...

[rmosolgo]

Ok, took another try at this. It should just listen for native unload even when doing turbolinks events.

[rmosolgo]

we don't do anything on unload anymore