chore: version packages - #581
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
blove
enabled auto-merge (squash)
September 5, 2026 19:46
Contributor
Vercel preview readyPreview: https://pretable-5aqynfs5c-cacheplane.vercel.app Updated automatically by the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@pretable/react@0.16.0
Minor Changes
The first two components of a kit the grid renders its own chrome from, and a (#580)
componentsprop to replace either with your own.PretableButton(two looks:ghost, the 24px action with a hover tint, andlink, plain accent text) andPretableIconButton(an icon-only button whosearia-labelis a required prop — omitting the accessible name is now acompile error, and an empty one warns in development). Both are always
type="button", passclassNameandstylestraight through, forward theirref, and carrydata-pretable-button/data-pretable-icon-button,data-pretable-variant(labelled buttons) anddata-pretable-sitefor stylingthrough the grid's usual attributes-and-tokens channel.
components={{ Button, IconButton }}on<PretableSurface>and<Pretable>replaces a component everywhere it appears — the tool panel, the header, the
group panel and the portalled filter dialog — and the replacement receives
exactly the props the built-in does,
siteincluded, so it can branch on wherein the grid it is. It must forward its
ref(under React 18,forwardRef; underReact 19 a plain
refprop): the grid anchors menus on and returns focus tothat node.
The grid's twelve plain push-buttons now render from these. Each keeps its
original attribute (
data-pretable-filter-clear,data-pretable-tool-reset,…), so selectors and stylesheets keyed on them keep working; the shared look
moved from twelve site rules onto the component rules, and every site's
computed box, colours and focus ring were measured before and after — no pixel
moved. Three things did change on purpose:
ClearandReset columns, and thefunnel, column-menu and chip-remove icon buttons, now wear the product's focus
ring rather than the browser's;
ClearandReset columnscarry the controlradius (visible only on that ring's corners); and the kit icon-button rule does
not set
position: relative— the three grid buttons that enlarge their hitarea with a
::afterdeclare it themselves, so a consumer rendering anabsolutely-positioned child inside
PretableIconButtonshould position thebutton explicitly.
Two smaller notes. The set of built-in
sitenames (PretableBuiltInButtonSite)grows additively — a new grid button may add one without a major bump. And the
two portalled surfaces that host these controls, the filter dialog and the
column menu, now declare
line-heightalongside the family, size and colourthey already declared:
font: inheriton a kit button had been pulling thehost page's line-height into
Clearand every menu item for a consumer with noCSS reset.
Patch Changes
9ddc19a]:@pretable/ui@0.16.0
Patch Changes
The first two components of a kit the grid renders its own chrome from, and a (#580)
componentsprop to replace either with your own.PretableButton(two looks:ghost, the 24px action with a hover tint, andlink, plain accent text) andPretableIconButton(an icon-only button whosearia-labelis a required prop — omitting the accessible name is now acompile error, and an empty one warns in development). Both are always
type="button", passclassNameandstylestraight through, forward theirref, and carrydata-pretable-button/data-pretable-icon-button,data-pretable-variant(labelled buttons) anddata-pretable-sitefor stylingthrough the grid's usual attributes-and-tokens channel.
components={{ Button, IconButton }}on<PretableSurface>and<Pretable>replaces a component everywhere it appears — the tool panel, the header, the
group panel and the portalled filter dialog — and the replacement receives
exactly the props the built-in does,
siteincluded, so it can branch on wherein the grid it is. It must forward its
ref(under React 18,forwardRef; underReact 19 a plain
refprop): the grid anchors menus on and returns focus tothat node.
The grid's twelve plain push-buttons now render from these. Each keeps its
original attribute (
data-pretable-filter-clear,data-pretable-tool-reset,…), so selectors and stylesheets keyed on them keep working; the shared look
moved from twelve site rules onto the component rules, and every site's
computed box, colours and focus ring were measured before and after — no pixel
moved. Three things did change on purpose:
ClearandReset columns, and thefunnel, column-menu and chip-remove icon buttons, now wear the product's focus
ring rather than the browser's;
ClearandReset columnscarry the controlradius (visible only on that ring's corners); and the kit icon-button rule does
not set
position: relative— the three grid buttons that enlarge their hitarea with a
::afterdeclare it themselves, so a consumer rendering anabsolutely-positioned child inside
PretableIconButtonshould position thebutton explicitly.
Two smaller notes. The set of built-in
sitenames (PretableBuiltInButtonSite)grows additively — a new grid button may add one without a major bump. And the
two portalled surfaces that host these controls, the filter dialog and the
column menu, now declare
line-heightalongside the family, size and colourthey already declared:
font: inheriton a kit button had been pulling thehost page's line-height into
Clearand every menu item for a consumer with noCSS reset.
@pretable/core@0.16.0
@pretable/stream-adapter@0.16.0