Document unsafe events on the container

Author: satya164

versioned_docs/version-7.x/navigation-container.md

@@ -285,6 +285,25 @@ const unsubscribe = navigationRef.addListener('options', (e) => {
 });
 ```
 
+##### `__unsafe_action__`
+
+The event is triggered whenever a navigation action is dispatched, and before the state changes from the action have been applied:
+
+```js
+const unsubscribe = navigationRef.addListener('__unsafe_action__', (e) => {
+  // The action object that was dispatched
+  console.log(e.data.action);
+
+  // Whether the action didn't result in any state changes
+  console.log(e.data.noop);
+
+  // Stack trace of the action, only available in development
+  console.log(e.data.stack);
+});
+```
+
+It's only intended for debugging purposes and shouldn't be used for app logic.
+
 ## Props
 
 ### `initialState`

versioned_docs/version-8.x/navigation-container.md

@@ -285,6 +285,47 @@ const unsubscribe = navigationRef.addListener('options', (e) => {
 });
 ```
 
+##### `__unsafe_action__`
+
+The event is triggered whenever a navigation action is dispatched, and before the state changes from the action have been applied:
+
+```js
+const unsubscribe = navigationRef.addListener('__unsafe_action__', (e) => {
+  // The action object that was dispatched
+  console.log(e.data.action);
+
+  // Whether the action didn't result in any state changes
+  console.log(e.data.noop);
+
+  // Stack trace of the action, only available in development
+  console.log(e.data.stack);
+});
+```
+
+It's only intended for debugging purposes and shouldn't be used for app logic.
+
+##### `__unsafe_event__`
+
+The event is triggered whenever an event is emitted by a navigator, and after all listeners have been called:
+
+```js
+const unsubscribe = navigationRef.addListener('__unsafe_event__', (e) => {
+  // The type of the event that was emitted
+  console.log(e.data.type);
+
+  // The data object passed when emitting the event
+  console.log(e.data.data);
+
+  // The key of the target route which received the event
+  console.log(e.data.target);
+
+  // Whether event.preventDefault() was called on this event
+  console.log(e.data.defaultPrevented);
+});
+```
+
+It's only intended for debugging purposes and shouldn't be used for app logic. To run app logic in response to an event, use the relevant navigator's [`listeners`](screen.md#listeners) prop or [`navigation.addListener`](navigation-object.md#addlistener).
+
 ## Props
 
 ### `initialState`

versioned_docs/version-8.x/upgrading-from-7.x.md

@@ -1279,6 +1279,23 @@ function MyHeader() {
 
 It renders a plain `View` on non-iPadOS platforms.
 
+### Navigation container ref now supports `__unsafe_event__`
+
+The navigation container ref now supports a `__unsafe_event__` event to listen for events emitted by navigators:
+
+```js
+const unsubscribe = navigationRef.addListener('__unsafe_event__', (e) => {
+  console.log(e.data.type);
+  console.log(e.data.data);
+  console.log(e.data.target);
+  console.log(e.data.defaultPrevented);
+});
+```
+
+This event is only intended for debugging purposes and shouldn't be used for app logic.
+
+See [NavigationContainer docs](navigation-container.md#__unsafe_event__) for more details.
+
 ### `useLogger` devtools now shows more information
 
 Previously, the `useLogger` devtools only showed navigation actions. It now shows the following additional information: