You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can migrate ClipboardManager to BlockHost.clipboard. This solves the problem of calling clipboard APIs from the blocks package and aligns more with our goal to build more editor modes as "block container" in @blocksuite/blocks. Ultimately the @blocksuite/editor package will be mainly a thin wrapper of different block containers (default page block, edgeless page block, mobile page block, etc.).
Also, this resolves the OpenBlockInfo conflicts.
It's a nice-to-have improvement. We can wait until the next housekeeping cleanup after our December release if we have a decent workaround.
So, should we now migrate or keep the status quo rather? I don't know if relocating will cause some other problems, for example, the previous call site will fail, Maybe need @zuoxiaodong0815 to tell me.
So, should we now migrate or keep the status quo rather? I don't know if relocating will cause some other problems, for example, the previous call site will fail, Maybe need @zuoxiaodong0815 to tell me.
Our discussion estimated that it may take a few days for the migration, so it would be fine to postpone this task for now.
We can migrate ClipboardManager to
BlockHost.clipboard
. This solves the problem of calling clipboard APIs from theblocks
package and aligns more with our goal to build more editor modes as "block container" in@blocksuite/blocks
. Ultimately the@blocksuite/editor
package will be mainly a thin wrapper of different block containers (default page block, edgeless page block, mobile page block, etc.).Also, this resolves the
OpenBlockInfo
conflicts.It's a nice-to-have improvement. We can wait until the next housekeeping cleanup after our December release if we have a decent workaround.
cc @DiamondThree @zuoxiaodong0815
The text was updated successfully, but these errors were encountered: