Repository navigation
Add grouped resource rows and release SDK 0.5.20 - #28
Merged
Merged
Conversation
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
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.
Resource lists can now render collapsible current-page groups through
rowGroupingonResourceListPageandDataTable. Group headers are presentation only: collapsing a group leaves all original rows in the SDK's page-wide and all-matching selection lifecycle, including confirmation, preflight, execution, refresh, and cleanup. Table and phone forms use the same contribution.Release SDK 0.5.20. Public declarations, grouped select-all accessibility text, documentation, packaged list guidance, changelog, and the packed consumer fixture are aligned. No backend, serialized contract, schema, fixture, protocol, theme-token, or persisted-storage changes are needed.
Validation:
npm run check, SDK tests (360 Vitest + 137 Node tests on Node 22 LTS), documentation build, package smoke test, and tarball contents checks passed. Regression tests cover explicit/all-matching selection, collapsed row selection, preflight/execution payloads and cleanup in table and stacked forms.