Uh oh!
There was an error while loading. Please reload this page.
Stabilize Components 3 consumer contracts - #169
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
This was referenced Aug 23, 2026
Closed
This was referenced Aug 23, 2026
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
Delivers the source-compatible Components stabilization work without changing the package's UI foundation. This release remains backed by PrimeReact 11, rendering consumers must continue to install its peers, and PrimeUI licensing still applies—including when Components is used as a wrapper. The renderer-independent React Aria architecture will be delivered separately as an explicitly documented and reviewed major release.
The reported
DataPagedefault-filter failure is covered by regression and browser evidence but was not reproducible on the current implementation.clientFilteringremains accepted as a deprecated no-op: filtering is page-local and server totals remain authoritative.Added
DatePickerInputidentity, disabled, read-only, and button-bar controls (DatePickerInput does not expose disabled, readOnly, id, or showButtonBar #154)Changed
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)Deprecated
clientFilteringfor source compatibility while making its page-local behavior explicit (clientFiltering is declared on DataTableForQuery, DataTableForObservableQuery and DataPage, forwarded by DataPage, and never read by any implementation #159)