Uh oh!
There was an error while loading. Please reload this page.
Complete the Components upstream compatibility roster - #168
Closed
woksin wants to merge 26 commits into
Closed
Conversation
Uh oh!
There was an error while loading. Please reload this page.
woksin
commented
Aug 23, 2026
ContributorAuthor
Superseded by #169 for the source-compatible stabilization release. The UI-kit-free/provider changes are intentionally deferred to a focused React Aria-based major architecture change so accessibility and correctness fixes are not coupled to a renderer migration. No commits from this PR were merged. |
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 freeto 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.
Summary
Completes the ready Components upstream roster as one coordinated release. The release hardens the PrimeReact 11 rendering contract, improves accessibility and localization, and adds a UI-kit-free Arc binding entry point. The previously reported default-filter failure is covered by regression and browser evidence but was not reproducible on the current implementation; PrimeUI licensing was already documented and configurable on
mainand was revalidated as part of this work.Added
DatePickerInputidentity, disabled, read-only, and button-bar controls (DatePickerInput does not expose disabled, readOnly, id, or showButtonBar #154)@cratis/components/core(Components has no UI-kit-free entry point: the Arc binding surface only ships inside the PrimeReact package #162)Changed
CratisComponentsConfigfrom PrimeReact renderer types while retaining direct-option compatibility (CratisComponentsConfig is Partial<PrimeReactProps>, so every consumer's root wiring is typed by a commercial third-party package #163)clientFilteringas a deprecated compatibility prop and documented server-side complete-result filtering (clientFiltering is declared on DataTableForQuery, DataTableForObservableQuery and DataPage, forwarded by DataPage, and never read by any implementation #159)Fixed
DataPagedefault filters without reproducing the reported empty-table failure (DataPage renders an empty table when given defaultFilters (any value, including {}) #149)DatePickerInputpass-through typing with the live input slot (DatePickerInput's pt type declares a pcInputText slot the runtime never emits, so the attributes are dropped and tsc stays green #150)DatePickerInputvalidation state from leaking to the DOM (DatePickerInput forwards invalid to the DOM, so React rejects it as a non-boolean attribute #151)