Revert "Add emoji variation selectors to all ✅ and ❌ across documentation"

This reverts commit 7bb73cc.

Author: escamoteur

docs/documentation/get_it/advanced.md

@@ -130,13 +130,13 @@ Pop DetailPage(item1)       → Release, refCount = 0 (service disposed)
 
 <strong>Benefits:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Service created synchronously (no async factory needed)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Async loading triggered in constructor</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ No duplicate loading for same item (checked before loading)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Automatic memory management via reference counting</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Reactive UI updates via `watch_it` (rebuilds on state changes)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ ChangeNotifier automatically disposed when refCount reaches 0</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Each itemId uniquely identified via `instanceName`</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Service created synchronously (no async factory needed)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Async loading triggered in constructor</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ No duplicate loading for same item (checked before loading)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Automatic memory management via reference counting</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Reactive UI updates via `watch_it` (rebuilds on state changes)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ ChangeNotifier automatically disposed when refCount reaches 0</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Each itemId uniquely identified via `instanceName`</li>
 </ul>
 
 <strong>Key Integration:</strong>
@@ -157,12 +157,12 @@ Only use `ignoreReferenceCount: true` when you're certain no other code is using
 
 ### When to Use Reference Counting
 
-✅️ <strong>Good use cases:</strong>
+✅ <strong>Good use cases:</strong>
 - Recursive navigation (same page pushed multiple times)
 - Services needed by multiple simultaneously active features
 - Complex hierarchical component structures
 
-❌️ <strong>Don't use when:</strong>
+❌ <strong>Don't use when:</strong>
 - Simple singleton that lives for app lifetime (use regular `registerSingleton`)
 - One-to-one widget-service relationship (use scopes)
 - Testing (use scopes to shadow instead)
@@ -192,15 +192,15 @@ Returns `null` instead of throwing an exception if the type is not registered. U
 
 <strong>When to use:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Optional features that may or may not be registered</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Feature flags (service registered only when feature enabled)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Platform-specific services (might not exist on all platforms)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Graceful degradation scenarios</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Optional features that may or may not be registered</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Feature flags (service registered only when feature enabled)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Platform-specific services (might not exist on all platforms)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Graceful degradation scenarios</li>
 </ul>
 
 <strong>Don't use when:</strong>
-- ❌️ The dependency is required - use `get<T>()` to fail fast
-- ❌️ Missing registration indicates a bug - exception is helpful
+- ❌ The dependency is required - use `get<T>()` to fail fast
+- ❌ Missing registration indicates a bug - exception is helpful
 
 ---
 

docs/documentation/get_it/async_objects.md

@@ -16,11 +16,11 @@ GetIt provides comprehensive support for asynchronous object creation and initia
 
 <strong>Key capabilities:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong><a href="#async-factories">Async Factories</a></strong> - Create new instances asynchronously on each access</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong><a href="#async-singletons">Async Singletons</a></strong> - Create singletons with async initialization</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong><a href="#dependency-management">Dependency Management</a></strong> - Automatically wait for dependencies before initialization</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong><a href="#startup-orchestration">Startup Orchestration</a></strong> - Coordinate complex initialization sequences</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong><a href="#manual-ready-signaling">Manual Signaling</a></strong> - Fine-grained control over ready state</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong><a href="#async-factories">Async Factories</a></strong> - Create new instances asynchronously on each access</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong><a href="#async-singletons">Async Singletons</a></strong> - Create singletons with async initialization</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong><a href="#dependency-management">Dependency Management</a></strong> - Automatically wait for dependencies before initialization</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong><a href="#startup-orchestration">Startup Orchestration</a></strong> - Coordinate complex initialization sequences</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong><a href="#manual-ready-signaling">Manual Signaling</a></strong> - Fine-grained control over ready state</li>
 </ul>
 
 ## Quick Reference

docs/documentation/get_it/faq.md

@@ -105,11 +105,11 @@ This error means you're trying to register the same type twice. Common causes:
 <strong>2. Registering inside build methods (hot reload issue)</strong>
 If you register services inside `build()` or `initState()`, hot reload will call it again.
 
-❌️ <strong>Wrong:</strong>
+❌ <strong>Wrong:</strong>
 
 <<< @/../code_samples/lib/get_it/my_app_example.dart#example
 
-✅️ <strong>Fix:</strong> Move registration to `main()` before `runApp()`:
+✅ <strong>Fix:</strong> Move registration to `main()` before `runApp()`:
 
 <<< @/../code_samples/lib/get_it/main_example_9.dart#example
 
@@ -199,9 +199,9 @@ Circular dependencies often mean:
 - Logic should be in a third service that coordinates both
 
 <strong>What NOT to do:</strong>
-❌️ Using `late` without proper initialization
-❌️ Using global variables to break the cycle
-❌️ Passing getIt instance around
+❌ Using `late` without proper initialization
+❌ Using global variables to break the cycle
+❌ Passing getIt instance around
 :::
 
 ## Why do I get "This instance is not available in GetIt" when calling signalReady?
@@ -271,17 +271,17 @@ Split registrations into separate functions that encapsulate scope management:
 
 <strong>Why functions matter:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong>Reusable</strong> - Call the same function when pushing scopes to reinitialize features</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong>Testable</strong> - Call specific registration functions in test setup</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong>Organized</strong> - Clear separation of concerns by feature/layer</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong>Centralized</strong> - All registration logic in one place, not scattered</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong>Reusable</strong> - Call the same function when pushing scopes to reinitialize features</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong>Testable</strong> - Call specific registration functions in test setup</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong>Organized</strong> - Clear separation of concerns by feature/layer</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong>Centralized</strong> - All registration logic in one place, not scattered</li>
 </ul>
 
 <strong>Don't:</strong>
-❌️ Scatter registration calls throughout your app
-❌️ Call registration methods from widget code
-❌️ Mix registration with business logic
-❌️ Duplicate registration code for different scopes
+❌ Scatter registration calls throughout your app
+❌ Call registration methods from widget code
+❌ Mix registration with business logic
+❌ Duplicate registration code for different scopes
 
 See [Scopes documentation](/documentation/get_it/scopes) for more on scope-based architecture.
 :::
@@ -292,21 +292,21 @@ See [Scopes documentation](/documentation/get_it/scopes) for more on scope-based
 
 Use <strong>scopes</strong> - they're designed for this exact use case:
 
-<strong>With Scopes (Recommended ✅️):</strong>
+<strong>With Scopes (Recommended ✅):</strong>
 
 <<< @/../code_samples/lib/get_it/on_login_example.dart#example
 
-<strong>Without Scopes (Not recommended ❌️):</strong>
+<strong>Without Scopes (Not recommended ❌):</strong>
 
 <<< @/../code_samples/lib/get_it/on_login.dart#example
 
 <strong>Why scopes are better:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Automatic cleanup and restoration</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Can't forget to re-register original services</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Dispose functions called automatically</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Cleaner, less error-prone code</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Can push multiple nested scopes</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Automatic cleanup and restoration</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Can't forget to re-register original services</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Dispose functions called automatically</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Cleaner, less error-prone code</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Can push multiple nested scopes</li>
 </ul>
 
 <strong>Use unregister when:</strong>
@@ -332,16 +332,16 @@ See [Scopes documentation](/documentation/get_it/scopes) for more patterns.
 
 <strong>When to use injectable:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Large apps with many services (50+)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ You prefer declarative over imperative code</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ You want dependency injection to be more automatic</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Large apps with many services (50+)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ You prefer declarative over imperative code</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ You want dependency injection to be more automatic</li>
 </ul>
 
 <strong>When manual registration is fine:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Small to medium apps (< 50 services)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ You prefer explicit, straightforward code</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ You want to avoid code generation build step</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Small to medium apps (< 50 services)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ You prefer explicit, straightforward code</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ You want to avoid code generation build step</li>
 </ul>
 
 <strong>Important:</strong> injectable is <strong>optional</strong>. get_it works great without it! The documentation here focuses on manual registration, which is simpler to learn and works for most apps.

docs/documentation/get_it/getting_started.md

@@ -17,11 +17,11 @@ next:
 
 <strong>Key benefits:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong>Extremely fast</strong> - O(1) lookup using Dart's Map</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong>Easy to test</strong> - Switch implementations for mocks in tests</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong>No BuildContext needed</strong> - Access from anywhere in your app (UI, business logic, anywhere)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong>Type safe</strong> - Compile-time type checking</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ <strong>No code generation</strong> - Works without build_runner</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong>Extremely fast</strong> - O(1) lookup using Dart's Map</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong>Easy to test</strong> - Switch implementations for mocks in tests</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong>No BuildContext needed</strong> - Access from anywhere in your app (UI, business logic, anywhere)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong>Type safe</strong> - Compile-time type checking</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ <strong>No code generation</strong> - Works without build_runner</li>
 </ul>
 
 <strong>Common use cases:</strong>
@@ -106,11 +106,11 @@ This is simpler and makes IDE navigation to implementation easier.
 
 <strong>When to use interfaces:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Multiple implementations (production vs test, different providers)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Platform-specific implementations (mobile vs web)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Feature flags to switch implementations</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Multiple implementations (production vs test, different providers)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Platform-specific implementations (mobile vs web)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Feature flags to switch implementations</li>
 </ul>
-- ❌️ Don't use "just because" - creates navigation friction in your IDE
+- ❌ Don't use "just because" - creates navigation friction in your IDE
 
 ---
 
@@ -168,28 +168,28 @@ As your app grows, you need to separate business logic from UI code. This makes
 <strong>Traditional approaches and their limitations:</strong>
 
 <strong>InheritedWidget / Provider:</strong>
-- ❌️ Requires `BuildContext` (not available in business layer)
-- ❌️ Adds complexity to widget tree
-- ❌️ Hard to access from background tasks, isolates
+- ❌ Requires `BuildContext` (not available in business layer)
+- ❌ Adds complexity to widget tree
+- ❌ Hard to access from background tasks, isolates
 
 <strong>Plain Singletons:</strong>
-- ❌️ Can't swap implementation for tests
-- ❌️ Tight coupling to concrete classes
-- ❌️ No lifecycle management
+- ❌ Can't swap implementation for tests
+- ❌ Tight coupling to concrete classes
+- ❌ No lifecycle management
 
 <strong>IoC/DI Containers:</strong>
-- ❌️ Slow startup (reflection-based)
-- ❌️ "Magic" - hard to understand where objects come from
-- ❌️ Most don't work with Flutter (no reflection)
+- ❌ Slow startup (reflection-based)
+- ❌ "Magic" - hard to understand where objects come from
+- ❌ Most don't work with Flutter (no reflection)
 
 <strong>get_it solves these problems:</strong>
 <ul style="list-style: none; padding-left: 0;">
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Access from anywhere without BuildContext</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Easy to mock for tests (register interface, swap implementation)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Extremely fast (no reflection, just Map lookup)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Clear and explicit (you see exactly what's registered)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Lifecycle management (scopes, disposal)</li>
-  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅️ Works in pure Dart and Flutter</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Access from anywhere without BuildContext</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Easy to mock for tests (register interface, swap implementation)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Extremely fast (no reflection, just Map lookup)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Clear and explicit (you see exactly what's registered)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Lifecycle management (scopes, disposal)</li>
+  <li style="padding-left: 1.5em; text-indent: -1.5em;">✅ Works in pure Dart and Flutter</li>
 </ul>
 
 <strong>Service Locator pattern:</strong>