Suggestion: deprecate this.$node

[necolas]

If there's still interest in eventually not depending on jQuery, this might be worth deprecating now as it seems to be the only place where we expose a jQuery wrapped object from the Flight API itself.

[giuseppeg]

+1

[kbingman]

Not depending on jQuery would be great. +1

[margaritis]

+1

[BugiDev]

+1
But i have a question, is there a way to get the selector which the component is attached to from inside the component?
In my app, i need to have the reference to node object of the component.

[giuseppeg]

@BugiDev no. You already have this.node though

[nkzawa]

What about this.select which returns a jQuery object?

[giuseppeg]

@nkzawa it'll return a NodeList I suppose that you can still convert to a jQuery object if you decide to use jQuery in your project

[nkzawa]

@giuseppeg Yeah, but that will break backward compatibility. We need a new method for that.

[giuseppeg]

@nkzawa it should be fairly easy to use advice to write a withJQuery mixin.

function withJQuery() {
  // define this.$node
  this.after('initialize', function () {
    this.$node = $(this.node);
  });

  // wrapper for select to return jQuery objects
  this.around('select', function (select) {
    return $(select([].slice.call(arguments, -1)));
  });
}

That you can manually mix with a component:

// Must be the first mixin
var MyComponent = flight.component(withJQuery, function () {});

Or we could decide to hook into the registry and do that automatically for you.

[nkzawa]

@giuseppeg It sounds great!

[karlhp]

+1

[tgvashworth]

This is closely related to #320, and will probably be fixed by that.

[giuseppeg]

@PhUU you can close this I guess

[tgvashworth]

Yep! Woohoo.