-
Notifications
You must be signed in to change notification settings - Fork 29.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for custom editors in the workbench #84672
Labels
custom-editors
Custom editor API (webview based editors)
plan-item
VS Code - planned item for upcoming
Milestone
Comments
bpasero
added a commit
that referenced
this issue
Nov 13, 2019
bpasero
added a commit
that referenced
this issue
Nov 13, 2019
bpasero
added a commit
that referenced
this issue
Nov 15, 2019
bpasero
added a commit
that referenced
this issue
Nov 17, 2019
bpasero
changed the title
Implement and adopt working copy service
Support for custom editors in the workbench
Nov 17, 2019
I think we settled on saving everything, even working copies from custom editors. |
3 tasks
No. It will remain as proposed api in 1.41 |
bpasero
added a commit
that referenced
this issue
Nov 21, 2019
bpasero
added
plan-item
VS Code - planned item for upcoming
and removed
debt
Code quality issues
labels
Dec 5, 2019
bpasero
added a commit
that referenced
this issue
Jan 10, 2020
All editor auto save functionality will now work for custom editors as well. |
bpasero
added a commit
that referenced
this issue
Jan 12, 2020
bpasero
added a commit
that referenced
this issue
Jan 14, 2020
This was referenced Jan 24, 2020
bpasero
added a commit
that referenced
this issue
Feb 18, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
custom-editors
Custom editor API (webview based editors)
plan-item
VS Code - planned item for upcoming
To support custom editors (#77131, #12176) we need our
IWorkingCopyService
to become more powerful, specifically taking over responsibility of:Work Areas:
save participants(text file based only, we do not plan for an API for other extensions to modify the custom editor data)The text was updated successfully, but these errors were encountered: