From 059f852bff813a3230c44a217866b032166f15be Mon Sep 17 00:00:00 2001
From: NullVoxPopuli <199018+NullVoxPopuli@users.noreply.github.com>
Date: Fri, 25 Apr 2025 14:29:13 -0400
Subject: [PATCH] Update initializers.md
---
guides/release/applications/initializers.md | 41 ---------------------
1 file changed, 41 deletions(-)
diff --git a/guides/release/applications/initializers.md b/guides/release/applications/initializers.md
index 25ed730829..55f7c91a71 100644
--- a/guides/release/applications/initializers.md
+++ b/guides/release/applications/initializers.md
@@ -18,47 +18,6 @@ Any asynchronous loading conditions (e.g. user authorization) are almost always
better handled in your application route's hooks,
which allows for DOM interaction while waiting for conditions to resolve.
-## Application Initializers
-
-Application initializers can be created with Ember CLI's `initializer` generator:
-
-```bash
-ember generate initializer shopping-cart
-```
-
-Let's customize the `shopping-cart` initializer to inject a `cart` property into all the routes in your application:
-
-```javascript {data-filename=app/initializers/shopping-cart.js}
-export function initialize(application) {
- application.inject('route', 'cart', 'service:shopping-cart');
-};
-
-export default {
- initialize
-};
-```
-
-## Application Instance Initializers
-
-Application instance initializers can be created with Ember CLI's `instance-initializer` generator:
-
-```bash
-ember generate instance-initializer logger
-```
-
-Let's add some simple logging to indicate that the instance has booted:
-
-```javascript {data-filename=app/instance-initializers/logger.js}
-export function initialize(applicationInstance) {
- let logger = applicationInstance.lookup('logger:main');
- logger.log('Hello from the instance initializer!');
-}
-
-export default {
- initialize
-};
-```
-
## Specifying Initializer Order
If you'd like to control the order in which initializers run, you can use the `before` and/or `after` options: