I am working in a Vue 2 project with nested ymaps, yarrays, and ytext (using YQuill). I (in a very hacky way) currently trigger redraws of the entire DOM in the doc.on(‘update’) handler, but this is proving to be quite slow as the content of the document grows. I’m trying to establish a way to attach additional metadata to each transaction so that each client can specifically target an update a particular component in my project. Initially I tried to use the origin parameter, but when using Y-Websocket with remote clients, the origin parameter is just the WebsocketProvider object with no indication of the operation origin.
Therefore, inspired by recommendations from previous forum posts, I am now experimenting with attaching an ‘event metadata’ yMap property with a timestamp, which individual clients can use as a queue of sorts to identify whether a new targeted redraw is necessary.
However, I am not sure how to do this with my YQuill editors, as the transaction logic is encapsulated in the library code. Edits in YQuill are actually the biggest pain point in my performance issues, as a remote client typing in a few words will trigger multiple redraws all at once, which really tanks the perfomance. Is there a way to include additional YMap edits with each YQuill transaction, or is there any other way to pass along metadata with a transaction (eg. modifying the YWebsocket code to pass along another origin-like parameter?) such that remote clients won’t be stuck in redraw loops? I’d appreciate any advice with the matter!