Hi @hediet is that something that you plan to do in the comming weeks? Or should I grab it and try to propose a change via PR?

Feel free to provide a PR, but I cannot guarantee you that it will get merged.
A PR might make it more likely that this issue gets resolved soon though.

That sounds good to me, thanks!
Do you preffer I add the change in to new proposed API, or extend the current ?

Please extend the current!

Going through what I think would be interesting to have in the additional metadata I settled on this:

• replacementRange
• partialAcceptanceKind
• documentVersionBeforeAcceptance
• text [very optional as it can be directly extracted using the replacement range + added chars]

The reason for that is, to be able to get a better visibility on what happened in the core without having to hack in addtional listeners for typing/cursor changes, directly from the partialAccepts. The data mentioned above would allow to easily reconstruct all edits that happened in a document, and allow for better post processing of the data.

I decided to split this in to 2 PRs:

• 1st - proposing the structural changes going through the whole stack (proposed API - extHost - mainThread - Core) and adding the base types
• 2nd - adding the other properties & convertors (which should be a smaller PR)

The 1st is being sent out right now, while the 2nd will be sent out after discussion, as there may be some points that we might want to clarify further.