Skip to content

Conversation

@ssreerama
Copy link
Contributor

@ssreerama ssreerama commented Dec 16, 2025

Pull Request Template – vscode-mssql

Description

This PR does the following changes to the repo

  • Copied extension from azuredatastudio repository to vscode-mssql/extensions/data-workspace/
  • Updated package.json - Changed name, publisher (ms-mssql), repository URLs, engines, scripts, and devDependencies
  • Fixed TypeScript config: Changed ES2024→ES2022 target, updated typings paths, fixed main entry point to "./out/src/main.js"
  • Created .vscodeignore: Properly configured to include compiled output for VSIX packaging
  • Added Azure DevOps pipeline: Created build template build-data-workspace.yml
  • Integrated GitHub Actions: Created custom build action and added full workflow coverage (build, lint, test, package, VSIX size tracking)
  • Configured localization: Added to extraction script, created l10n/ directory, updated LocProject.json
  • Updated VS Code debugging: Added data-workspace to launch.json "Run All Extensions" configuration
  • Updated documentation: Added data-workspace to README.md
  • Temporary ADS dependencies: Commented out ADS git imports with TODO markers for Phase 2 cleanup
  • Telemetry event package info get method fixed with correct path
  • ESLint: eslint 9 migration and Auto-fixed 3030 formatting errors - now passing with 0 errors, 80 warnings
  • DevDependencies: Added all required packages and matched versions with mssql extension

Test fixes:

  • Package.json updated with test path to discover the tests
  • Test framework conversion, replaced ADS specific @microsoft/azdata-test with VsCode's @vscode/test-electron
  • Added vscode.workspace.findFiles stubs to allow extension activation in tests Mock improvements: Changed activation stubs to return Promises for few tests
  • Dialog tests: Commented out entire test bodies with TODO explaining they need VS Code UI migration

Code Changes Checklist

  • New or updated unit tests added
  • All existing tests pass (npm run test)
  • Code follows contributing guidelines
  • Telemetry/logging updated if relevant
  • No regressions or UX breakage

Reviewers: Please read our reviewer guidelines

@github-actions
Copy link

github-actions bot commented Dec 16, 2025

PR Changes

Category Target Branch PR Branch Difference
vscode-mssql VSIX 5285 KB 5284 KB ⚪ -1 KB ( 0% )
sql-database-projects VSIX 5668 KB 5668 KB ⚪ 0 KB ( 0% )
data-workspace VSIX null KB 532 KB ⚪ 532 KB ( 0% )

@codecov-commenter
Copy link

codecov-commenter commented Dec 16, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.90%. Comparing base (6ebbedc) to head (a17ad30).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #20813   +/-   ##
=======================================
  Coverage   65.90%   65.90%           
=======================================
  Files         210      210           
  Lines       19991    19991           
  Branches     2596     2596           
=======================================
  Hits        13175    13175           
  Misses       6718     6718           
  Partials       98       98           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

….yml

- Updated build-and-test.yml workflow to include data-workspace:
- Added data-workspace to localization extraction config (scripts/localization-extract.js)
- Updated VS Code launch configuration to include data-workspace for debugging (.vscode/launch.json)
- Added data-workspace documentation to main README.md (repository layout and development sections)
- Updated GitHub workflows README to reflect all three extensions
@ssreerama ssreerama self-assigned this Dec 16, 2025
@ssreerama ssreerama added this to the January 2026 Release milestone Dec 16, 2025
@ssreerama ssreerama marked this pull request as ready for review December 16, 2025 18:54
@ssreerama ssreerama changed the title Initial changes: moving data workspace to vscode with working build Initial changes: Decoupling data workspace extension from ADS to vscode with working build Dec 16, 2025
@Benjin
Copy link
Contributor

Benjin commented Dec 16, 2025

Looks like neither the linter nor tests are running correctly in the pipelines. Linter should run and pass, and the tests should run successfully (but okay if they're not all passing because that'll be a follow-up).

@ssreerama
Copy link
Contributor Author

Done. The linter is now working, and the test suites are being discovered and running successfully. There are a few test failures remaining, which I will address in my next PR

"license": "SEE LICENSE IN LICENSE.txt",
"icon": "images/extension.png",
"aiKey": "29a207bb14f84905966a8f22524cb730-25407f35-11b6-4d4e-8114-ab9e843cb52f-7380",
"homepage": "https://github.com/Microsoft/vscode-mssql/blob/main/extensions/data-workspace/README.md",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Microsoft" should be lower-cased in this URL

Comment on lines +25 to +28
"url": "https://github.com/Microsoft/vscode-mssql.git"
},
"bugs": {
"url": "https://github.com/Microsoft/vscode-mssql/issues"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same with these two

Comment on lines +7 to +10
// Note for debugging the VS Code version of the extension, currently you will need to modify
// the package.json and manually copy over the values from package.vscode.json into package.json
// (otherwise you'll get errors since other extensions depend on an extension with the name
// data-workspace-vscode, not data-workspace)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these comments still true?

Maybe the need reversing: do we now build data-workspace-vscode by default, and need to swap things around when building for ADS?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any scope to build the data-workspace from VS Code for ADS before it’s retired? My understanding is that with Phase 2 (removing ADS dependency completely), we won’t need to link ADS at all. Please correct me if I’m wrong.

@Benjin
Copy link
Contributor

Benjin commented Dec 17, 2025

Commented out ADS git imports with TODO markers for Phase 2 cleanup

Can you add a comment in the code where this is happening for what "phase 2 cleanup" entails and add a link to a github issue for tracking that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants