Jake Donham

a workaround is to avoid named imports of types, so instead of ``` import { UrqlQueryResult, UrqlMutationResult } from '../useUrqlEnchanceHook' ``` do ``` import * as UseUrqlEnchanceHook from '../useUrqlEnchanceHook' ```...

@ulion I would love your feedback on this

I'm going to experiment with calling React hooks from the existing `decorate` function (see comments on PR #4484) to see if we can achieve the goal without changing the API.

I think putting decorations in the Slate core is a good idea. But to support dynamic use cases, I think the core needs some built-in notion of reactive update: when...

If I understand you correctly, the existing decoration mechanism already supports this—the `decorate` function returns a list of `Range`s, which can cross node boundaries. Internally Slate splits the ranges at...

that's true, but it's not because decorations can't be cross-node. To generate cross-node match ranges I think you'd need to do something like `Editor.string`, i.e. iterate through all the text...

another way we could address this would be to avoid needing to self-sandbox the Markdown, Processing, etc. blocks, see discussion at https://github.slack.com/archives/C01JU2DH6V7/p1646936045898539

It is true. The only way to do it at the moment is to manually copy the deriving binary to a bin directory. It looks like Raphael Proust and Henri...

Well, my intention was to be maintainer for deriving, but I don't have the time. I will see if Raphael / Gregoire want to be maintainers.

Thank you for the bug report. I think both these cases could be fixed: the first by applying the gotten value to any extra arguments, the second by generating a...