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

[vscode] proposed API evolution and menu declarations between 1.90 and 1.91 - Work in Progress #13871

Open
15 of 16 tasks
rschnekenbu opened this issue Jul 2, 2024 · 0 comments
Open
15 of 16 tasks
Assignees
Labels
vscode issues related to VSCode compatibility

Comments

@rschnekenbu
Copy link
Contributor

rschnekenbu commented Jul 2, 2024

As of today, VS Code 1.91 not yet released. Evaluation based on main branch, commit 01b9e01

Sources

  • commit ref for tags

  • command used

    • git difftool -d 89de5a8..01b9e01 -- src/vscode-dts/ on vscode repo
    • command: git submodule foreach "grep -irn enabledApiProposals --include=package.json | cut -d ':' -f 1 | xargs jq --raw-output '{filename: input_filename, enabledApiProposals: .enabledApiProposals}'" > ./vscode-builtins-enabled-proposals-1.91.0.txt on vscode-builtin-extensions repo, on commit 01b9e01
    • git difftool -d 89de5a8..01b9e01 -- src/vs/workbench/services/actions/common/menusExtensionPoint.ts on vscode repo

Evaluation

  • vscode.proposed.aiTextSearchProvider.d.ts: updated in 1.91, not used in builtins
  • vscode.proposed.attributableCoverage.d.ts, updated in 1.91, only used in selfhost test provider workspace extension
  • vscode.proposed.authGetSessions.d.ts: updated in 1.91, used in tests and microsoft-authentification extension. This microsoft-authentification builtin is in the list of ignored plugins for Theia.
  • vscode.proposed.chatParticipantPrivate.d.ts: updated in 1.91, only used in tests
  • vscode.proposed.chatProvider.d.ts: updated in 1.91, only used in tests
  • vscode.proposed.chatVariableResolver.d.ts: updated in 1.91, only used in tests
  • vscode.proposed.commentReveal.d.ts: new in 1.91, not used in builtins
  • vscode.proposed.commentThreadApplicability.d.ts: updated in 1.91, not used in builtins
  • vscode.proposed.createFileSystemWatcher.d.ts: updated in 1.91, used in typescript builtins. One parameter was optional, it is now required (createFileSystemWatcher#excludes)
  • vscode.proposed.fileComments.d.ts: updated in 1.91, not used in builtins
  • vscode.proposed.fileSearchProvider.d.ts: updated in 1.91, only used in tests
  • vscode.proposed.inlineCompletionsAdditions.d.ts: updated in 1.91, not used in builtins
  • vscode.proposed.lmTools.d.ts: new in 1.91, only used in tests
  • vscode.proposed.mappedEditsProvider.d.ts: updated in 1.91 (only a comment change on a stubbed API), used in typescript builtins
  • vscode.proposed.scmHistoryProvider.d.ts: updated in 1.91, used in tests and git builtins. Still the same ignored optional property (see [vscode] support proposed API scmHistoryProvider introduced with vscode 1.83 #13064)
  • vscode.proposed.terminalShellIntegration.d.ts: updated in 1.91 (onlyu comments), only used in tests.
@rschnekenbu rschnekenbu added the vscode issues related to VSCode compatibility label Jul 2, 2024
@rschnekenbu rschnekenbu self-assigned this Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
vscode issues related to VSCode compatibility
Projects
None yet
Development

No branches or pull requests

1 participant