Skip to content
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

Expose monaco-editor instance on vscode.TextEditor #88879

Closed
shaman-apprentice opened this issue Jan 17, 2020 · 2 comments
Closed

Expose monaco-editor instance on vscode.TextEditor #88879

shaman-apprentice opened this issue Jan 17, 2020 · 2 comments
Assignees
Labels
*out-of-scope Posted issue is not in scope of VS Code

Comments

@shaman-apprentice
Copy link

I would like to access the monaco-editor instance on a vscode.TextEditor directly. For example to insert ViewZones (see #88483 for detailed motivation).

This would make #85682 obsolete. In general I assume a better experience for developing extensions with direct monaco-editor access, as it removes an abstraction layer, which must be learnt, maintained (and waited for to be created in the first place if it doesn't already exist).

@jrieken jrieken added the *out-of-scope Posted issue is not in scope of VS Code label Jan 20, 2020
@vscodebot
Copy link

vscodebot bot commented Jan 20, 2020

We closed this issue because we don't plan to address it in the foreseeable future. You can find more detailed information about our decision-making process here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Jan 20, 2020
@jrieken
Copy link
Member

jrieken commented Jan 20, 2020

There is the renderer and the extension host process. The first is for the UX, the second is a dedicated process in which extensions run. There is no way to expose the Monaco-editor API in the latter because of this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

2 participants