Closed fundon closed 2 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
blocksuite | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jul 10, 2024 3:18am |
Add the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge.
You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.
master
This stack of pull requests is managed by Graphite. Learn more about stacking.
Join @fundon and the rest of your teammates on Graphite
You should remove the duplicate components in this graphite stack.
The next PR will include it in stack. But there are many files to change. Step by step.
- The base direction is to avoid more
<affine-xxx>
components since for common components, they should be moving towards reusable components that are not specific to Affine. So I'd suggest making the naming<editor-toolbar>
,<editor-toolbar-separator>
,<editor-menu-xxx>
.
Good idea. Make sense.
- Are these components now ready to be reused in doc editor? If not, keeping the
<edgeless-xxx>
naming may make more sense.
Sure, they should all be common components.
Saul-Mirone
added this pull request to the Graphite merge queue.Saul-Mirone
merged this pull request with the Graphite merge queue.
Closes: BS-702
editor-toolbar
This is a generic toolbar component that can be used in different modes.
Scenarios:
Includes components:
editor-toolbar
editor-icon-button
editor-menu-button
editor-menu-content
editor-menu-action
editor-toolbar-separator
These duplicate components will be removed in the following PRs: See
packages/blocks/src/root-block/edgeless/components/buttons
.