Use Mixins and allow option for no Initializers about ember-tooltips HOT 3 CLOSED

Definitely valid points. I think there's some value in the 'plug and play' nature of initializers so perhaps an option, as you suggested, to manually import the code that's refactored into a mixin would be the best option. I'd happily accept a PR as I won't be working much until next week but either way would like to make these improvements.

The option is probably best set in the config/environment file because it's not really affecting the broccoli build, just the browser code. So something like:

/* jshint node: true */

module.exports = function(environment) {
  var ENV = {
    modulePrefix: 'dummy',
    podModulePrefix: 'dummy/resources',
    environment: environment,
    baseURL: '/',
    locationType: 'auto',
    EmberENV: {
      FEATURES: {
        // Here you can enable experimental features on an ember canary build
        // e.g. 'with-controller': true
      }
    },

    APP: {
      // Here you can pass flags/options to your application instance
      // when it is created
    },

    tooltips: {
      setupInInitializer: true, // or false
    }
  };
}

from ember-tooltips.

This will be fixed by #3, which is currently up for review.

from ember-tooltips.

#3 merged into master and released as 0.2.0.

from ember-tooltips.