Repository navigation
feat(ui): SidePanel actions in the header (ui 0.10.0) - #12
Merged
Merged
Conversation
The item's own buttons (« Modifier », a « … » menu) sit in the panel header, before the walk and the close button; the footer stays for the form's cancel and save.
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.
SidePanelgets anactionsprop: the item's own buttons (« Modifier », a « … » menu) in the panel header, before the walk and the close button. The footer stays for a form's cancel and save. This is what the speaker panel and the organigram's role panel boards draw.ui/src/side-panel.tsx:actions?: ReactNode, rendered in the header.@unitae/ui0.10.0 (no breaking change), README row updated.Checked:
vitest run(62 tests),tsc6 --noEmit, the build,biome checkon the changed files,pnpm install --frozen-lockfile.After merging, push the tag
ui-v0.10.0to publish.