pulse_view_components 0.3.0 → 0.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0f457ccc7139eadce5f0c7902605b37cf2d8a1fb9400db8159d46fce2ee9fda9
-  data.tar.gz: a419c33680af5ffb6a2c26c6f1198e3824afc3424f27d40f5e7b095b8198163a
+  metadata.gz: ee83609e86903aa5b7772032bc8a1620c7f21c804aabd5da7812baa8b533add3
+  data.tar.gz: 83c778fc2e8b4d90b7f4f9079ea6eb8818aef9befdc39f1766ad12c3edfc1ede
 SHA512:
-  metadata.gz: c57be4358008253cd9ca9d1a8ea18c5895104346466f707a7adbdb86683714f61174c6282547a30c6351c4b05c3e522710cdc129b8a6c1e456c42ca5a4752c63
-  data.tar.gz: 39f968613cece83349c1883622012f40abd8dc9e72aacce646558c7462cb535dcda74945f40254200cd568627e97eeb83442e7630ac2fbb33059ef9721dee249
+  metadata.gz: 5ffe1a1b23f94f71142348ede4ce6cc447d585d5ba104a87866b38f614c46fed26455a8cf79a5a7d58d69639fea8654b851ed0d7383ee768aeef3fcdd7618993
+  data.tar.gz: 87a6ce613ba799b5d74b9308da262cdf574ac1772eccdbe46d4fee62f241037fb1ba5fcba80f8f64bd7b027a87653c2a51dd05aa1eb9287164e7223e4e045fa7

data/CHANGELOG.md

@@ -8,6 +8,117 @@ While the major version is `0`, a minor bump may carry a breaking change.
 
 ## [Unreleased]
 
+## [0.4.1] - 2026-11-13
+
+### Fixed
+
+- The gem now declares `slim` and `turbo-rails` as dependencies and requires
+  them, along with `inline_svg` and `active_link_to`, when it loads. Before,
+  components only rendered if the host app listed all four gems in its own
+  Gemfile. Without `inline_svg`, any component that renders an icon raised
+  `NoMethodError` on `inline_svg_tag`.
+
+### Changed
+
+- `rails` is capped below 9 until we test against it.
+- Development Ruby moved to 3.4.12. The gem still supports Ruby >= 3.4.0.
+
+## [0.4.0] - 2026-10-19
+
+Upgrades to Tailwind CSS 4. This is a breaking change for apps that pass
+classes through `classes:`, because the prefix is now written as a leading
+variant (`pulse:bg-primary` rather than `pulse-bg-primary`). See Changed.
+
+### Added
+
+- Components declare a status of `:alpha`, `:beta`, `:stable` or
+  `:deprecated`, read with `Pulse::Thing.status`. `ActionList`, `NavList` and
+  `Counter` are alpha. `BorderBox`, `Flash` and `Layout` are beta. See the
+  README for what each level means.
+- An `ActionList` Lookbook preview.
+- A `neutral` semantic color, backed by a new `gray` palette token that copies
+  Tailwind 4's gray.
+- A Foundations > Colors Lookbook page that shows the semantic colors and the
+  palettes behind them.
+
+### Fixed
+
+- `ActionList::Divider` with `scheme: :filled` draws its top and bottom
+  borders again. It used class names that Tailwind 4 does not generate.
+- `ActionList`, `ActionList::Heading` and every `NavList` group raised on
+  render because they had no template.
+- `NavList` items with sub-items raised, and their sub-items never rendered.
+- `BorderBox` rendered a `system_arguments_denylist` HTML attribute.
+  `BaseComponent` now consumes the denylist and raises outside production when
+  a denied argument is passed, so `BorderBox.new(pt: 2)` now raises. In
+  production, or with `PULSE_WARNINGS_DISABLED`, it drops the denied argument
+  from the output instead.
+- `Forms::ErrorExplanation` rendered "Header" as its heading unless the app
+  defined `errors.template.header`. It now ships a default heading and still
+  prefers the app's translation. In a locale with no app translation it
+  shows the English heading instead of raising.
+- `Forms::ErrorExplanation` counted every error in its heading but listed only
+  one per attribute, so two errors on `title` read "2 errors" above one item.
+  The heading now counts the listed errors.
+- Several components used `text-gray`, which Tailwind never defined, so their
+  text inherited its colour. They now use neutral-700: `Badge` (`invited`,
+  `active` and `disabled` schemes), the secondary `Button`, the `Modal` title
+  and close button, inactive `NavLink`s, `Table` headers, cells and
+  pagination, and the link in an error `Toast`.
+- The `Table` body and `Text` `caption1` and `caption2` used the undefined
+  `leading-extra-snug` and `leading-extra-tight`, so no line height applied.
+  They now use `leading-snug` and `leading-tight`.
+
+### Changed
+
+- Components use `neutral-*` color classes instead of `gray-*`. The colors
+  are unchanged. The build no longer includes Tailwind's `gray` utilities, so
+  a `pulse:*-gray-*` class passed in through `classes:` now has no styles.
+  Use `pulse:*-neutral-*` instead.
+- **Breaking:** upgraded to Tailwind CSS 4. The class prefix is now written as
+  a leading variant, so `pulse-bg-primary` becomes `pulse:bg-primary` and
+  `hover:pulse-text-white` becomes `pulse:hover:text-white`. Classes passed to
+  components through `classes:` must use the new form.
+- `Forms::ErrorExplanation` now inherits from `Pulse::Component`. It merges
+  `classes:` with `tailwind_merge` and rejects a `tag:` argument.
+- The primary `Button` green shifted. Tailwind 4 redefined its palette in
+  oklch, so `green-700` moved from `#15803d` to about `#008236`. The blue-700
+  focus outline shifted the same way.
+- The `error` and `danger` reds shifted slightly. Every shade of the
+  `amaranth` palette they map to changed, for example 700 moved from `#ee2d5b`
+  to `#ee2d4b`.
+- Some utilities were renamed by Tailwind 4 (`outline-none` is now
+  `outline-hidden`, `start-0` is now `inset-s-0`).
+- CSS custom properties from the theme are now emitted with the prefix, for
+  example `--pulse-color-primary`.
+- `tailwind_merge` dependency raised to `~> 1.5`, which understands Tailwind 4
+  class syntax.
+- The Tailwind config moved from `tailwind.config.js` into the stylesheet as
+  CSS-first configuration.
+
+### Removed
+
+- `@tailwindcss/aspect-ratio` and `@tailwindcss/typography`, which no component
+  used. `aspect-*` utilities are built into Tailwind 4.
+- The unused `peer-unchecked` variant. Tailwind 4's `peer-not-checked` covers
+  it.
+- `postcss.config.js`, `postcss` and `autoprefixer`. The Tailwind 4 CLI does
+  not read the PostCSS config.
+- Utilities named after the raw palettes, such as `pulse-bg-coral-red-500`.
+  The palettes are now `--palette-*` theme variables outside the colour
+  namespace. Use the semantic names (`primary`, `secondary`, `tertiary`,
+  `success`, `danger`, `error`, `neutral`) instead.
+
+### Internal
+
+- Development Node moved to 22, since Tailwind 4 needs Node 20 or later.
+- `chokidar` is now a direct dev dependency. `esbuild.config.mjs` imports it,
+  and it previously arrived only through Tailwind 3.
+- Design tokens split into `tokens.primitives.css` (palettes) and
+  `tokens.system.css` (semantic colours).
+- Development `view_component` moved to 4.16, along with other development gem
+  updates.
+
 ## [0.3.0] - 2026-08-28
 
 No breaking changes. The component API, the gemspec constraints and the
@@ -80,7 +191,9 @@ No breaking changes. The component API, the gemspec constraints and the
 
 - Initial release.
 
-[Unreleased]: https://github.com/100yrs/pulse_view_components/compare/v0.3.0...HEAD
+[Unreleased]: https://github.com/100yrs/pulse_view_components/compare/v0.4.1...HEAD
+[0.4.1]: https://github.com/100yrs/pulse_view_components/compare/v0.4.0...v0.4.1
+[0.4.0]: https://github.com/100yrs/pulse_view_components/compare/v0.3.0...v0.4.0
 [0.3.0]: https://github.com/100yrs/pulse_view_components/compare/v0.2.1...v0.3.0
 [0.2.1]: https://github.com/100yrs/pulse_view_components/compare/v0.2.0...v0.2.1
 [0.2.0]: https://github.com/100yrs/pulse_view_components/compare/v0.1.1...v0.2.0

data/README.md

@@ -14,6 +14,32 @@ Render Pulse ViewComponents:
 <%= render(Pulse::Badge.new(scheme: :primary)) { 'Primary' } %>
 ```
 
+## Component status
+
+Each component declares how complete it is. Check it with
+`Pulse::ActionList.status`. Lookbook shows the status after the name of any
+component that is not stable.
+
+| Status | Meaning |
+| --- | --- |
+| `stable` | Complete and safe to use. |
+| `beta` | Core usage works. Some documented options are not implemented. |
+| `alpha` | Incomplete. Features may be broken, unstyled or missing, and the API may change without notice. |
+| `deprecated` | Scheduled for removal. |
+
+Components that are not stable:
+
+| Component | Status | Gaps |
+| --- | --- | --- |
+| `ActionList` | alpha | Select variants, trailing actions, tooltips, avatar items and the `:inset` scheme do not work. |
+| `NavList` | alpha | Avatar items raise. Sub-items cannot be collapsed. The show-more item has no JavaScript. |
+| `Counter` | alpha | Renders unstyled. |
+| `BorderBox` | beta | `padding:` and row `scheme:` have no effect. |
+| `Flash` | beta | `dismissible: true` raises. `full: true` has no effect. |
+| `Layout` | beta | Main `width:` options other than `:full` have no effect. |
+
+The comment above each `status` call in the source lists what is missing.
+
 ## Dependencies
 
 - [Stimulus](https://stimulus.hotwired.dev/)

data/app/assets/builds/js/pulse_view_components.js

@@ -9441,20 +9441,20 @@
       this.lastFocusedElement = document.activeElement;
       enter(this.wrapperTarget);
       enter(this.bodyTarget);
-      document.body.classList.add("pulse-overflow-hidden");
+      document.body.classList.add("pulse:overflow-hidden");
     }
     close(e) {
       leave(this.wrapperTarget);
       leave(this.bodyTarget).then(() => {
         this.element.remove();
       });
-      document.body.classList.remove("pulse-overflow-hidden");
+      document.body.classList.remove("pulse:overflow-hidden");
       if (this.lastFocusedElement) this.lastFocusedElement.focus();
       this.element.closest("turbo-frame").src = void 0;
     }
     autoClose(e) {
       this.element.remove();
-      document.body.classList.remove("pulse-overflow-hidden");
+      document.body.classList.remove("pulse:overflow-hidden");
     }
     handleSubmit = (e) => {
       if (e.detail.success) {