Re: [I] VS Code Extensions should keep their Editors in sync even when files change externally [incubator-kie-issues]

["Josephblt (via GitHub)" <gi...@apache.org>]

Josephblt commented on issue #119:
URL: https://github.com/apache/incubator-kie-issues/issues/119#issuecomment-2020770768

   Hello @tiagobento, @jomarko. There is a solution using VS Code API FileSystemWatcher implemented in the Extended Services VS Code Extension. We could replicate this for the other editors. I could move the solution to the base code [vscode-extension](https://github.com/Josephblt/kie-tools/tree/main/packages/vscode-extension) and do only the necessary changes directly to the editors.
   
   As for the conflict handling between file sources, there is no standard way. But, we could do something similar to this:
   https://code.visualstudio.com/assets/api/ux-guidelines/examples/notification.png
   It is just a matter of using a more appropriate message and accurate buttons. For example, instead of "Accept remote" - Accept local we go with Keep changes - Discard changes. Please let me know what you guys think.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org