docs: Add DestroyRef.destroyed and usage in lifecycle guide (#64422)

SkyZeroZx · thePunderWoman · commit 9b494c7de585 · 2025-10-21T15:12:50.000Z
PR Close #64422
diff --git a/adev/src/content/guide/components/lifecycle.md b/adev/src/content/guide/components/lifecycle.md
@@ -161,6 +161,12 @@ destroyed.
 You can also use `DestroyRef` to keep setup code close to cleanup code, rather than putting
 all cleanup code in the `ngOnDestroy` method.
 
+##### Detecting instance destruction
+
+`DestroyRef` provides a `destroyed` property that allows checking whether a given instance has already been destroyed. This is useful for avoiding operations on destroyed components, especially when dealing with delayed or asynchronous logic.
+
+By checking `destroyRef.destroyed`, you can prevent executing code after the instance has been cleaned up, avoiding potential errors such as `NG0911: View has already been destroyed.`.
+
 ### ngDoCheck
 
 The `ngDoCheck` method runs before every time Angular checks a component's template for changes.
@@ -237,7 +243,7 @@ See [Using DOM APIs](guide/components/dom-apis) for guidance on working with the
 
 Render callbacks do not run during server-side rendering or during build-time pre-rendering.
 
-#### after*Render phases
+#### after\*Render phases
 
 When using `afterEveryRender` or `afterNextRender`, you can optionally split the work into phases. The
 phase gives you control over the sequencing of DOM operations, letting you sequence _write_
diff --git a/packages/core/src/linker/destroy_ref.ts b/packages/core/src/linker/destroy_ref.ts
@@ -20,6 +20,8 @@ const EXECUTE_CALLBACK_IF_ALREADY_DESTROYED = false;
  * is injected in a component or directive, the callbacks run when that component or
  * directive is destroyed. Otherwise the callbacks run when a corresponding injector is destroyed.
  *
+ * @see [Lifecycle DestroyRef](guide/components/lifecycle#destroyref)
+ *
  * @publicApi
  */
 export abstract class DestroyRef {
@@ -43,11 +45,17 @@ export abstract class DestroyRef {
    * // stop the destroy callback from executing if needed
    * unregisterFn();
    * ```
+   *
+   * @see [Lifecycle DestroyRef](guide/components/lifecycle#destroyref)
+   *
    */
   abstract onDestroy(callback: () => void): () => void;
 
   /**
    * Indicates whether the instance has already been destroyed.
+   *
+   * @see [Detecting instance destruction](guide/components/lifecycle#detecting-instance-destruction)
+   *
    */
   abstract get destroyed(): boolean;
 
