change undeveloped warning text

Archmonger · Archmonger · commit 260b5e5972b9 · 2023-06-30T16:40:11.000-07:00
diff --git a/docs/src/learn/add-react-to-an-existing-project.md b/docs/src/learn/add-react-to-an-existing-project.md
@@ -1,4 +1,4 @@
-!!! warning "In Progress"
+!!! warning "Planned / Undeveloped"
 
     This feature is planned, but not yet developed.
 
diff --git a/docs/src/learn/python-in-psx-with-curly-braces.md b/docs/src/learn/python-in-psx-with-curly-braces.md
@@ -1,4 +1,4 @@
-!!! warning "In Progress"
+!!! warning "Planned / Undeveloped"
 
     This feature is planned, but not yet developed.
 
diff --git a/docs/src/learn/react-developer-tools.md b/docs/src/learn/react-developer-tools.md
@@ -1,4 +1,4 @@
-!!! warning "In Progress"
+!!! warning "Planned / Undeveloped"
 
     This feature is planned, but not yet developed.
 
diff --git a/docs/src/learn/tutorial-material-ui.md b/docs/src/learn/tutorial-material-ui.md
@@ -1,4 +1,4 @@
-!!! warning "In Progress"
+!!! warning "Planned / Undeveloped"
 
     This tutorial is planned, but is missing a key feature before this page can be written.
 
diff --git a/docs/src/learn/tutorial-react-bootstrap.md b/docs/src/learn/tutorial-react-bootstrap.md
@@ -1,4 +1,4 @@
-!!! warning "In Progress"
+!!! warning "Planned / Undeveloped"
 
     This tutorial is planned, but is missing a key feature before this page can be written.
 
diff --git a/docs/src/learn/writing-markup-with-psx.md b/docs/src/learn/writing-markup-with-psx.md
@@ -1,4 +1,4 @@
-!!! warning "In Progress"
+!!! warning "Planned / Undeveloped"
 
     This feature is planned, but not yet developed.
 
diff --git a/docs/src/reference/use-deferred-value.md b/docs/src/reference/use-deferred-value.md
@@ -1,3 +1,7 @@
+!!! warning "Planned / Undeveloped"
+
+    This feature is planned, but not yet developed.
+<!-- 
 ## Overview
 
 <p class="intro" markdown>
@@ -988,4 +992,4 @@ Also, unlike with debouncing or throttling, deferred re-renders done by `useDefe
 
 If the work you're optimizing doesn't happen during rendering, debouncing and throttling are still useful. For example, they can let you fire fewer network requests. You can also use these techniques together.
 
-</DeepDive>
+</DeepDive> -->
diff --git a/docs/src/reference/use-id.md b/docs/src/reference/use-id.md
@@ -1,9 +1,9 @@
-!!! warning "In Progress"
+!!! warning "Planned / Undeveloped"
 
     This feature is planned, but not yet developed.
 
     See [this issue](https://github.com/reactive-python/reactpy/issues/985) for more details.
-
+<!-- 
 ## Overview
 
 <p class="intro" markdown>
@@ -285,4 +285,4 @@ root2.render(<App />);
 input {
 	margin: 5px;
 }
-```
+``` -->
diff --git a/docs/src/reference/use-imperative-handle.md b/docs/src/reference/use-imperative-handle.md
@@ -1,4 +1,8 @@
-## Overview
+!!! warning "Planned / Undeveloped"
+
+    This feature is planned, but not yet developed.
+
+<!-- ## Overview
 
 <p class="intro" markdown>
 
@@ -290,4 +294,4 @@ export default AddComment;
 
 **If you can express something as a prop, you should not use a ref.** For example, instead of exposing an imperative handle like `{ open, close }` from a `Modal` component, it is better to take `isOpen` as a prop like `<Modal isOpen={isOpen} />`. [Effects](/learn/synchronizing-with-effects) can help you expose imperative behaviors via props.
 
-</Pitfall>
+</Pitfall> -->
diff --git a/docs/src/reference/use-insertion-effect.md b/docs/src/reference/use-insertion-effect.md
@@ -1,3 +1,7 @@
+!!! warning "Planned / Undeveloped"
+
+    This feature is planned, but not yet developed.
+<!-- 
 <Pitfall>
 
 `useInsertionEffect` is for CSS-in-JS library authors. Unless you are working on a CSS-in-JS library and need a place to inject the styles, you probably want [`useEffect`](/reference/react/useEffect) or [`useLayoutEffect`](/reference/react/useLayoutEffect) instead.
@@ -132,4 +136,4 @@ If you insert styles during rendering and React is processing a [non-blocking up
 
 `useInsertionEffect` is better than inserting styles during [`useLayoutEffect`](/reference/react/useLayoutEffect) or [`useEffect`](/reference/react/useEffect) because it ensures that by the time other Effects run in your components, the `<style>` tags have already been inserted. Otherwise, layout calculations in regular Effects would be wrong due to outdated styles.
 
-</DeepDive>
+</DeepDive> -->
diff --git a/docs/src/reference/use-layout-effect.md b/docs/src/reference/use-layout-effect.md
@@ -1,3 +1,7 @@
+!!! warning "Planned / Undeveloped"
+
+    This feature is planned, but not yet developed.
+<!-- 
 <Pitfall>
 
 `useLayoutEffect` can hurt performance. Prefer [`useEffect`](/reference/react/useEffect) when possible.
@@ -683,4 +687,4 @@ However, if you're running into this problem, you have a few different options:
 
 -   Alternatively, you can render a component with `useLayoutEffect` only after hydration. Keep a boolean `isMounted` state that's initialized to `false`, and set it to `true` inside a `useEffect` call. Your rendering logic can then be like `return isMounted ? <RealContent /> : <FallbackContent />`. On the server and during the hydration, the user will see `FallbackContent` which should not call `useLayoutEffect`. Then React will replace it with `RealContent` which runs on the client only and can include `useLayoutEffect` calls.
 
--   If you synchronize your component with an external data store and rely on `useLayoutEffect` for different reasons than measuring layout, consider [`useSyncExternalStore`](/reference/react/useSyncExternalStore) instead which [supports server rendering.](/reference/react/useSyncExternalStore#adding-support-for-server-rendering)
+-   If you synchronize your component with an external data store and rely on `useLayoutEffect` for different reasons than measuring layout, consider [`useSyncExternalStore`](/reference/react/useSyncExternalStore) instead which [supports server rendering.](/reference/react/useSyncExternalStore#adding-support-for-server-rendering) -->
diff --git a/docs/src/reference/use-sync-external-store.md b/docs/src/reference/use-sync-external-store.md
@@ -1,3 +1,7 @@
+!!! warning "Planned / Undeveloped"
+
+    This feature is planned, but not yet developed.
+<!-- 
 ## Overview
 
 <p class="intro" markdown>
@@ -422,4 +426,4 @@ function ChatIndicator({ userId }) {
 
 	// ...
 }
-```
+``` -->
diff --git a/docs/src/reference/use-transition.md b/docs/src/reference/use-transition.md
@@ -1,3 +1,7 @@
+!!! warning "Planned / Undeveloped"
+
+    This feature is planned, but not yet developed.
+<!-- 	
 ## Overview
 
 <p class="intro" markdown>
@@ -1580,4 +1584,4 @@ function setState() {
 		// ... schedule an urgent state update ...
 	}
 }
-```
+``` -->

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-!!! warning "In Progress"`
	`1`	`+!!! warning "Planned / Undeveloped"`
`2`	`2`
`3`	`3`	`This feature is planned, but not yet developed.`
`4`	`4`