Jeff Sisson

Roger that. I'm trying to implement [access control](https://grafast.org/grafast/access-control) in a way that's field-aware — e.g. I'd like to propagate request-scoped authorization details down into field-scoped resolvers, in order to early...

This bug is still real on master, and this fork definitely fixes it — though this fix doesn't account for a similar bug (https://github.com/leafo/lessphp/issues/507) which affects `from` and `to` in...

> here we eschew prosemirror-view's EditorView entirely, in place of a custom-built React component it doesn't look like any of the implementation here required changes to any of the existing...

> What kind of compatibility requirement are you imagining, though? @smoores-dev I'm picturing: - Changes to non-`prosemirror-view` classes that depend on corresponding changes in `prosemirror-view` - Changes other libraries depend...

(I am going to ask Marijn about this and will try to ferry any notable details from that conversation back here!)

quoting Marijn: > > e.g. where a bug fix requires a change to prosemirror-state and prosemirror-view, or prosemirror-tables and prosemirror-view (or something like that) > > This is very unlikely....

> Are you suggesting two different APIs exposed by this library, the current one and the one proposed by this PR? Is there any code on this PR that breaks...

> Essentially none of the old hooks, aside from maybe useEditorState, make much sense in the context of the component; and meanwhile there will need to be several new hooks...