@recursica/adapter-mantine-v8 1.2.2 → 1.3.1

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # @recursica/adapter-mantine-v8
 
+## 1.3.1
+
+### Patch Changes
+
+- 4e1ecc2: Updated @recursica/adapter-common, adapter-tester and storybook-template to their latest releases.
+- 4e1ecc2: FileUpload is now capped at the global form-field max-width instead of filling its whole container.
+- 4e1ecc2: FileInput keeps a fixed height when a file is added, FileUpload width is also enforced at the layout level, and vertical Stepper, Tabs and Switch no longer add Mantine spacing on top of the Recursica gap tokens.
+- 4e1ecc2: Menu WithSubmenus story no longer forces a 200px width, so it uses the Recursica menu min-width token.
+- 4e1ecc2: Panel rounds only the corners facing the page, and RadioGroup/CheckboxGroup `side-by-side` layouts now stack vertically instead of wrapping in a row.
+- 4e1ecc2: Panel width now follows the Forge `max-width` token (capped at the viewport width) instead of Mantine's 440px default.
+- 4e1ecc2: Vertical SegmentedControl now uses a container radius concentric with its items and a correct horizontal divider between items.
+
+## 1.3.0
+
+### Major Changes
+
+- 31bb5be: `Pagination` now renders Recursica Buttons whose style and size come from the Forge manifest, so `RecursicaThemeProvider` needs the `manifest` prop or Pagination throws; its compound parts are rebuilt on `usePagination` and Mantine's `Pagination` props are no longer passed through.
+- 31bb5be: `Grid` is now `LayoutGrid` (`LayoutGrid.Col`) and follows Forge's breakpoint-aware layout grids (columns, gutters, margin, including breakpoint-map spans); it no longer accepts the `columns` prop. Use Mantine's Grid directly for a fixed N-column grid.
+
+### Minor Changes
+
+- 31bb5be: New opt-in `breakpointsFromRecManifest` builds a Mantine `theme.breakpoints` object from the Forge manifest's layout grids.
+
 ## 1.2.2
 
 ### Patch Changes

package/OVERSTYLING.md

@@ -39,6 +39,6 @@ Available Recursica layout tokens:
 
 ## Primitive Layout Components Exemption
 
-Unlike complex UI components (Buttons, Tabs, Inputs) which are strictly protected, **Primitive Layout Components** (`Flex`, `Stack`, `Group`, `Container`, `Grid`) are entirely exempt from the `RecursicaOverStyled` gatekeeper.
+Unlike complex UI components (Buttons, Tabs, Inputs) which are strictly protected, **Primitive Layout Components** (`Flex`, `Stack`, `Group`, `Container`, `LayoutGrid`) are entirely exempt from the `RecursicaOverStyled` gatekeeper.
 
 Because the entire functional purpose of these components is structural layout composition, developers are free to pass any standard Mantine width, height, padding, margin, gap, and alignment property directly to them without needing to flag `overStyled={true}`. The internal custom token mapper (such as converting `gap="rec-md"`) is still active natively on these wrappers.

package/SETUP.md

@@ -43,11 +43,12 @@ Before consuming Recursica components, integrate the CSS and design tokens into
    ```tsx
    import { MantineProvider } from "@mantine/core";
    import { RecursicaThemeProvider } from "@recursica/adapter-mantine-v8";
+   import manifest from "./path/to/recursica_manifest.json";
 
    function App() {
      return (
        <MantineProvider>
-         <RecursicaThemeProvider theme="light">
+         <RecursicaThemeProvider theme="light" manifest={manifest}>
            {/* Your App Components */}
          </RecursicaThemeProvider>
        </MantineProvider>
@@ -55,7 +56,37 @@ Before consuming Recursica components, integrate the CSS and design tokens into
    }
    ```
 
-4. **Configure PostCSS Plugin (Optional but Recommended)**: It is highly recommended (but optional) to install the `@recursica/recursica-postcss-vars` plugin to verify that Recursica CSS variables are properly connected in case they change.
+   Pass the parsed `recursica_manifest.json` from your Forge export as `manifest`. Components that are configured by it (currently `Pagination`, for its Button variants) read it from here and throw if it's missing.
+
+4. **Align Mantine's breakpoints with Forge's (Optional but Recommended)**: Forge defines your layout grids (columns, gutters, margin) per breakpoint, and they switch via plain CSS `@media`. Mantine's responsive props (`span={{ base: 12, md: 6 }}`, `visibleFrom`, and Flex/Stack/Group props) switch at `theme.breakpoints` instead, which Forge never edits. If the two differ, a page changes layout at two different widths. `breakpointsFromRecManifest` builds a `theme.breakpoints` object from the `recursica_manifest.json` in your Forge export, so both switch at the same widths:
+
+   ```tsx
+   import { MantineProvider, createTheme } from "@mantine/core";
+   import {
+     RecursicaThemeProvider,
+     breakpointsFromRecManifest,
+   } from "@recursica/adapter-mantine-v8";
+   import manifest from "./path/to/recursica_manifest.json";
+
+   // e.g. { mobile: "0px", tablet: "481px", default: "781px" } when Forge defines extra grids
+   const theme = createTheme({
+     breakpoints: breakpointsFromRecManifest(manifest),
+   });
+
+   function App() {
+     return (
+       <MantineProvider theme={theme}>
+         <RecursicaThemeProvider theme="light" manifest={manifest}>
+           {/* Your App Components */}
+         </RecursicaThemeProvider>
+       </MantineProvider>
+     );
+   }
+   ```
+
+   Each non-default grid starts at its `min-width` (a grid with only a `max-width` starts at `0px`), and the `default` grid is named `default` and starts one pixel past the widest `max-width`. If your manifest only defines the `default` grid (the stock export), it returns `{}` and your theme is unchanged. Mantine merges these with its defaults, so `xs`–`xl` still exist at Mantine's widths; use Forge's names (`mobile`, `tablet`, ...) in responsive props to switch where Forge does. The result is a plain object you can edit, and nothing applies it automatically. See the [LayoutGrid usage guide](src/components/LayoutGrid/USAGE.md).
+
+5. **Configure PostCSS Plugin (Optional but Recommended)**: It is highly recommended (but optional) to install the `@recursica/recursica-postcss-vars` plugin to verify that Recursica CSS variables are properly connected in case they change.
 
    Install the plugin as a dev dependency:
 
@@ -76,7 +107,7 @@ Before consuming Recursica components, integrate the CSS and design tokens into
    };
    ```
 
-5. **Configure ESLint Plugin (Optional but Recommended)**: It is highly recommended (but optional) to install `@recursica/eslint-plugin`, which flags use of the `overStyled` escape-hatch prop so it stays easy to audit.
+6. **Configure ESLint Plugin (Optional but Recommended)**: It is highly recommended (but optional) to install `@recursica/eslint-plugin`, which flags use of the `overStyled` escape-hatch prop so it stays easy to audit.
 
    Install the plugin as a dev dependency: