DEV: Remove `discourse/components/glimmer` superclass (#17877)
This was a temporary solution while we updated the resolver and migrated all our singletons to true ember services. Now that's done, we can switch to use `@glimmer/component` directly, and explicitly inject services as required.
This commit is contained in:
parent
2c5ab47204
commit
636be8cac5
|
@ -1,24 +0,0 @@
|
||||||
import GlimmerComponent from "@glimmer/component";
|
|
||||||
import { inject as service } from "@ember/service";
|
|
||||||
|
|
||||||
/*
|
|
||||||
Glimmer components are not EmberObjects, and therefore do not support automatic
|
|
||||||
injection of the things defined in `pre-initializers/inject-discourse-objects`.
|
|
||||||
|
|
||||||
This base class provides an alternative. All these references are looked up lazily,
|
|
||||||
so the performance impact should be negligible
|
|
||||||
*/
|
|
||||||
|
|
||||||
export default class DiscourseGlimmerComponent extends GlimmerComponent {
|
|
||||||
@service appEvents;
|
|
||||||
@service store;
|
|
||||||
@service("search") searchService;
|
|
||||||
@service keyValueStore;
|
|
||||||
@service pmTopicTrackingState;
|
|
||||||
@service siteSettings;
|
|
||||||
@service messageBus;
|
|
||||||
@service currentUser;
|
|
||||||
@service session;
|
|
||||||
@service site;
|
|
||||||
@service topicTrackingState;
|
|
||||||
}
|
|
Loading…
Reference in New Issue