-
Notifications
You must be signed in to change notification settings - Fork 555
Initial changes: Decoupling data workspace extension from ADS to vscode with working build #20813
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
base: main
Are you sure you want to change the base?
Conversation
PR Changes
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ 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:
|
….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
|
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). |
…metry package info method
… UI tests and todo comment to revist with ADS code removal
|
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", |
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.
"Microsoft" should be lower-cased in this URL
| "url": "https://github.com/Microsoft/vscode-mssql.git" | ||
| }, | ||
| "bugs": { | ||
| "url": "https://github.com/Microsoft/vscode-mssql/issues" |
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.
same with these two
| // 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) |
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.
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?
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.
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.
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? |
Pull Request Template – vscode-mssql
Description
This PR does the following changes to the repo
Test fixes:
Code Changes Checklist
npm run test)Reviewers: Please read our reviewer guidelines