@mittwald/flow-react-components 0.2.0-alpha.1004 → 0.2.0-alpha.1005

package/AGENTS.md

@@ -264,8 +264,18 @@ props to hide.
 
 ## Misc
 
-- Feature flags: `src/flags.ts` holds a few behavior toggles; there is no formal
-  policy around them.
+- Application-wide component defaults: `ComponentDefaultsProvider`
+  (`src/components/ComponentDefaultsProvider/`) is where a behavior default that
+  an application should be able to set **once** belongs. Add the setting to the
+  `ComponentDefaults` interface plus its built-in value in
+  `builtInComponentDefaults`, and read it with `useComponentDefaults("<Name>")`
+  at the place that decides. Resolution order: local prop → provider →
+  deprecated `flags` → built-in default. This is not a replacement for
+  `PropsContext`: a UI component clears the props context for its children, so
+  PropsContext cannot carry an app-wide default past the first UI ancestor.
+- Feature flags: `src/flags.ts` is the deprecated predecessor of the
+  `ComponentDefaultsProvider`. Assigned flags still act as an application-wide
+  default (and warn via `useWarnDeprecation`); do not add new ones.
 - `SettingsProvider` (`src/components/SettingsProvider/`) is the built-in
   persistence for component settings (e.g. `List` remembering its view
   settings), with pluggable backends (localStorage by default). Internal

package/CHANGELOG.md

@@ -3,6 +3,12 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [0.2.0-alpha.1005](https://github.com/mittwald/flow/compare/0.2.0-alpha.1004...0.2.0-alpha.1005) (2026-08-06)
+
+### Features
+
+* **components:** add ComponentDefaultsProvider for application-wide defaults ([#2796](https://github.com/mittwald/flow/issues/2796)) ([c043f6c](https://github.com/mittwald/flow/commit/c043f6c89b2aa2bb669355014698e57cd81ea796))
+
 # [0.2.0-alpha.1004](https://github.com/mittwald/flow/compare/0.2.0-alpha.1003...0.2.0-alpha.1004) (2026-08-06)
 
 ### Bug Fixes

package/MIGRATION.md

@@ -1,5 +1,46 @@
 # Migrations
 
+## From version `0.2.0-alpha.1004` to `>=0.2.0-alpha.1005`
+
+### Closing a Modal with unsaved changes is confirmed by default
+
+A `Modal` that contains a react-hook-form `<Form>` now asks for confirmation
+before it closes while the form is _dirty_ — previously this required the
+`requireCloseModalConfirmationOnUnsavedChanges` flag. After a successful submit
+or a `form.reset()` the modal closes right away, and actions in the
+`<ActionGroup />` as well as the close button in the heading still close it
+immediately.
+
+Nothing to do if you had the flag enabled. To keep the previous behavior, switch
+the default off (see below).
+
+### `flags` is replaced by the ComponentDefaultsProvider
+
+The global `flags` object is deprecated. Application-wide defaults are defined
+with the `<ComponentDefaultsProvider />` instead, which additionally works per
+subtree:
+
+```diff
+- import { flags } from "@mittwald/flow-react-components";
+-
+- flags.requireCloseModalConfirmationOnUnsavedChanges = false;
+- flags.disableInitialListSuspenseBoundaries = true;
++ import { ComponentDefaultsProvider } from "@mittwald/flow-react-components";
++
++ <ComponentDefaultsProvider
++   defaults={{
++     Form: { confirmModalCloseOnUnsavedChanges: false },
++     List: { disableInitialSuspenseBoundary: true },
++   }}
++ >
++   <App />
++ </ComponentDefaultsProvider>
+```
+
+Assigning a flag keeps working — it acts as the application-wide default below
+the provider and logs a deprecation warning — but the flags will be removed in a
+future release.
+
 ## From version `0.2.0-alpha.779` to `>=0.2.0-alpha.780`
 
 ### CartesianChart