You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should avoid depending on the vscode typescript module as much as possible because it's only available when the extension is run within vscode itself.
This is fine for using the extension normally, but it complicates tests a lot because we have to create manual mocks for anything we import from vscode that has a runtime component (ie not types).
The worst offender is Uri, for which there is a partial replacement through the vscode-uri package, but it's not a perfect match. Some tedious manual mocking is still required.
The ultimate goal would be to have no dependencies on vscode outside of the extension.ts entrypoint.
The text was updated successfully, but these errors were encountered:
We should avoid depending on the
vscode
typescript module as much as possible because it's only available when the extension is run within vscode itself.This is fine for using the extension normally, but it complicates tests a lot because we have to create manual mocks for anything we import from vscode that has a runtime component (ie not types).
The worst offender is
Uri
, for which there is a partial replacement through thevscode-uri
package, but it's not a perfect match. Some tedious manual mocking is still required.The ultimate goal would be to have no dependencies on
vscode
outside of theextension.ts
entrypoint.The text was updated successfully, but these errors were encountered: