Skip to content

Overhaul linting, formatting, and testing infrastructure #5190

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

Merged
merged 8 commits into from
May 15, 2025

Conversation

andyleejordan
Copy link
Member

Replaces #5188 with a whole overhaul of our linting, formatting, and testing infrastructure.

@andyleejordan andyleejordan marked this pull request as ready for review May 15, 2025 21:01
@Copilot Copilot AI review requested due to automatic review settings May 15, 2025 21:01
@andyleejordan andyleejordan requested a review from a team as a code owner May 15, 2025 21:01
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR completely overhauls our linting, formatting, and testing infrastructure. It replaces legacy import and configuration patterns with modern TypeScript type imports and updated configuration files, while also revising workspace settings and dependency versions.

Reviewed Changes

Copilot reviewed 34 out of 34 changed files in this pull request and generated no comments.

Show a summary per file
File Description
src/logging.ts Modernized logger initialization using nullish assignment and updated imports
src/features/* Updated type imports and removed eslint-disable comments for empty interfaces
src/extension.ts Adjusted import types and refined inline comments
pwsh-extension-dev.code-workspace Revised workspace settings with updated file patterns and new extension recommendations
package.json, eslint.config.mjs, etc. Updated dependency versions and overhauled configuration to support new standards
Comments suppressed due to low confidence (2)

src/logging.ts:143

  • The use of the nullish assignment operator (??=) is concise; ensure that the target environment and TypeScript version fully support this syntax.
this._channel ??= window.createOutputChannel(this.channelName, {log: true});

pwsh-extension-dev.code-workspace:314

  • The new 'outFiles' pattern is more restrictive; make sure it matches all emitted JavaScript files required for proper source map support.
"${workspaceFolder:Client}/dist/*.js"

@andyleejordan andyleejordan added Area-Build & Release Area-Test Area-Tech Debt Issues for Tech Debt Days! Issue-Enhancement A feature request (enhancement). labels May 15, 2025
Copy link
Collaborator

@SeeminglyScience SeeminglyScience left a comment

Choose a reason for hiding this comment

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

LGTM!

Copy link
Collaborator

@JustinGrote JustinGrote left a comment

Choose a reason for hiding this comment

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

LGTM! Nice work on the test fixes. Just some future notes.

"@vscode/vsce": "^3.3.0",
"esbuild": "^0.25.1"
"@vscode/vsce": "^3.3.2",
"esbuild": "^0.25.4"
},
"optionalDependencies": {
Copy link
Collaborator

Choose a reason for hiding this comment

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

We probably should document somewhere why optionalDependencies vs devdependencies

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm really hoping it changes when I get back to trying #5063

@andyleejordan andyleejordan merged commit 722af37 into main May 15, 2025
8 checks passed
@andyleejordan andyleejordan deleted the lint-overhaul branch May 15, 2025 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Build & Release Area-Tech Debt Issues for Tech Debt Days! Area-Test Issue-Enhancement A feature request (enhancement).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants