-
Notifications
You must be signed in to change notification settings - Fork 6k
Expose actions registry in IDE API #701
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
Conversation
f171819
to
1167833
Compare
We need |
@code-asher yea my bad, exposed. |
@@ -1,6 +1,9 @@ | |||
// tslint:disable no-any | |||
|
|||
import { ITerminalService } from "vs/workbench/contrib/terminal/common/terminal"; | |||
import { IWorkbenchActionRegistry } from 'vs/workbench/common/actions'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Importing from here won't work right?
It will within the project, but importing inside another would leave these unresolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure what you mean.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those files aren't included in the ide-api
package so anything that imports it won't be able to resolve those types (only applies if you're using TypeScript of course). We'll want to fully encapsulate the API within the typings file before publishing a new version of the API.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not just use the vscode typings? Why are we wrapping?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'd have to include VS Code's code with the ide-api
package. Since the files we import may import other files, it'd probably be easiest to just import all of VS Code, but it feels odd (to me) to include the entirety of VS Code just for the types.
The way VS Code does it is to have an entirely separate typings file like we're doing here and redefine all the types. Actually maybe we can just import their typings file and re-export some things from it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually that wouldn't work because that doesn't include types for their internal methods, just what they expose to extensions.
* upstream/master: Show hidden files by default Fix human readable byte size when zero Expose actions registry (coder#701) Set NODE_ENV and VERSION when building (coder#700) Don't try to create builtin extensions directory Suppress "disconnected" notification on extension host Extra extensions directories (coder#694) Updated Data Directory Flag (coder#664) Remove broken links (coder#671)
No description provided.