You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the new component integration tests, it's easier to give a component access to a container for testing. However, the current way the initializer is set up, it requires an application to be present, which isn't available in a unit test.
I think this could be solved by using an instance-initializer and calling register and injection on the instance that gets passed through. For instance, check out how ember-i18n does this.
The thing that I'm not sure about is how you could make this backwards compatible for pre 1.12 Ember apps.
The text was updated successfully, but these errors were encountered:
In Ember I18n he has both an initializer and an instance-initializer (the initializer flavor just imports and calls the instance-intiailizer). I think this is how he manages backwards compatibility.
Think this issue is resolved! Moved the latest version over to a service based approach for customizations. Would love to know if this made your life easier (if you're still even using this library)
With the new component integration tests, it's easier to give a component access to a container for testing. However, the current way the initializer is set up, it requires an
application
to be present, which isn't available in a unit test.I think this could be solved by using an instance-initializer and calling
register
andinjection
on theinstance
that gets passed through. For instance, check out how ember-i18n does this.The thing that I'm not sure about is how you could make this backwards compatible for pre 1.12 Ember apps.
The text was updated successfully, but these errors were encountered: