@mittwald/flow-codemods 1.2.0-next.2 → 1.2.0-next.3

package/dist/migrations.generated.js

@@ -19,7 +19,7 @@ export const migrations = [
         kind: "deprecation",
         action: "manual",
         remotePackage: true,
-        apply: "Replace `SegmentedControl` with `Tabs` when the selection switches displayed content, or with `RadioGroup` when it sets a value. Pick per usage — this is a structural change, not a rename.",
+        apply: "Replace `SegmentedControl` with `Tabs` when the selection switches displayed content, or with `RadioGroup` when it sets a value. Pick per usage. The two directions cost very different amounts of work. Towards `RadioGroup` it is a prop-compatible rename: `SegmentedControl` → `RadioGroup` and `Segment` → `RadioButton` (always `RadioButton`, not `Radio`; it takes exactly `Segment`'s props), with `value`/`defaultValue`/`onChange` and a `Label` child all carrying over. Only `containerBreakpointSize` has no counterpart, and the joined row is not reproduced. Towards `Tabs` it is structural: the state props are `selectedKey`/`defaultSelectedKey` rather than `value`/`defaultValue`, there is no `Label` slot (the group label moves to the surrounding `Heading`, or to `aria-label` on `Tabs` when it should not be visible, or goes away), and the switched panels move inside the tabs — where they stay mounted, so form fields in them keep their registration.",
     },
     {
         id: "align-to-combine",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mittwald/flow-codemods",
-  "version": "1.2.0-next.2",
+  "version": "1.2.0-next.3",
   "type": "module",
   "description": "Codemods and an upgrade CLI for consumers of Flow, mittwald's design system",
   "homepage": "https://flow.mittwald.de",
@@ -36,5 +36,5 @@
     "vitest": "^4.1.11",
     "yaml": "^2.8.1"
   },
-  "gitHead": "2b9fab062a58e7cf148ab0ce120ea2798d7c5b9b"
+  "gitHead": "308539dabbc9256b6481b6291035ed69207e021a"
 }