Combo Box remote options mode erases tom select's load callback

[adanselm]

I'd like to combine remote options with the virtual scroll tom select plugin, which requires a custom load callback.
I can't do that because the combo-box-hook.js replaces this callback even if it's defined in my globalOpts:

    if (remoteOptionsEventName) {
      tomSelectOptions.load = (query, callback) => {
        const handleServerReply = (payload, ref) => {
          const resultsJSON = payload.results.map(({ text, value }) => ({
            text,
            value,
          }));

          callback(resultsJSON);
        };

Behaviour could be to not overwrite the callback if I defined my own in globalOpts and let me handle the complex loading on my own (if that's even possible in tom select to use both plugins at the same time).

[mitkins]

So you can avoid the code above if you don't set the remote_options_event_name attribute on the component. That would let you keep your globalOpts. I'm going to add a snippet of code that will add a warning in the JavaScript console if the user has set both tom_select_options_global_variable and remote_options_event_name.

However, that does mean that you'd have to handle both plugins from one load function. If you do this from the globalOpts you'll lose the convenience of the interop code that's in the hook. The following covers receiving Live View events:

https://hexdocs.pm/phoenix_live_view/js-interop.html#handling-server-pushed-events

But with regards to pushing events you won't have access to remoteOptionsTarget. I'm sure there will be some way to achieve this, but I haven't looked into it.

It might be more convenient to update the hook itself with the virtual scroll code. At least if you did this initially, you could test Tom Select with virtual scrolling and remote loading.