Best way to analyse transactions in PluginView.update

Hello. Is there a way to analyse the transactions that changed the state in a PluginView.update? I know I can use the plugin state for this, even storing the transactions if necessary, but it would be better if I could directly inspect the transactions in the update function.

The view and view plugins don’t have access to transactions in ProseMirror, only to the updated state.


Thanks! As a suggestion, if possible I think it would be interesting to access the list of transactions in view plugins. Sometimes I want to trigger an action outside of Prosemirror based on a transaction, and to do this I have to use the plugin state. It would be simpler to only inspect the transaction without messing with the state.

Yes, it would. But at this point making that possible would be a breaking change, so that’s not going to happen.

1 Like