refactor: add async query for dom mutation scenario

[Saul-Mirone]

This PR adds async version of query functions to avoid the ambiguity requestAnimationFrame call when updating dom.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
blocksuite	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Mar 10, 2023 at 2:06AM (UTC)
blocksuite-react	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Mar 10, 2023 at 2:06AM (UTC)

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[lawvs]

I try to deprecate the concept of richText. Therefore, I think asyncSetVRangeForVirgo or asyncSetVRange would be better.

See #1626

[zqran]

Can async/await syntax be used here, I think the code format will be more uniform

[Saul-Mirone]

I didn't use the asyn function here is because I want to handle the promise error in the function and make sure when it is called, users won't need to handle it manually.

[zqran]

I think it is equivalent to write like this:

async function asyncSetVRange(model: BaseBlockModel, vRange: VRange) {
  try {
    const richText = await asyncGetRichTextByModel(model)
    richText?.vEditor?.setVRange(vRange);
  } catch (e) {
    throw e;
  }
}

[doodlewind]

This try/catch looks redundant.

[Saul-Mirone]

I think it is equivalent to write like this:

async function asyncSetVRange(model: BaseBlockModel, vRange: VRange) {

  try {

    const richText = await asyncGetRichTextByModel(model)

    richText?.vEditor?.setVRange(vRange);

  } catch (e) {

    throw e;

  }

}

IMO they won't be equal. When you're using try catch in an async function, it will reject the error, and if the place where it called doesn't catch it, it will be a floating promise error. But, nevermind, it's not that important in this case.

[doodlewind]

Great work!