Skip to content

Update eslint from 8 to 9.#14157

Open
sean-mcmanus wants to merge 19 commits intomainfrom
seanmcm/updateEslint
Open

Update eslint from 8 to 9.#14157
sean-mcmanus wants to merge 19 commits intomainfrom
seanmcm/updateEslint

Conversation

@sean-mcmanus
Copy link
Contributor

@sean-mcmanus sean-mcmanus commented Feb 2, 2026

This was mostly done by Copilot Agent mode...well, the initial edit...I had to fix a bunch of stuff it did.

@sean-mcmanus sean-mcmanus requested a review from a team as a code owner February 2, 2026 22:02
@github-project-automation github-project-automation bot moved this to Pull Request in cpptools Feb 2, 2026
@sean-mcmanus sean-mcmanus requested a review from Copilot February 2, 2026 22:03

This comment was marked as resolved.

@sean-mcmanus sean-mcmanus marked this pull request as draft February 2, 2026 22:10
@sean-mcmanus

This comment was marked as resolved.

@sean-mcmanus sean-mcmanus requested a review from Copilot February 2, 2026 22:58
@sean-mcmanus sean-mcmanus marked this pull request as ready for review February 2, 2026 22:59

This comment was marked as resolved.

@sean-mcmanus sean-mcmanus requested a review from Copilot February 2, 2026 23:08

This comment was marked as resolved.

@sean-mcmanus sean-mcmanus requested a review from Colengms February 3, 2026 00:20
@sean-mcmanus

This comment was marked as resolved.

Colengms
Colengms previously approved these changes Feb 3, 2026
@sean-mcmanus
Copy link
Contributor Author

@bobbrow Were all your concerns addressed?

@bobbrow
Copy link
Member

bobbrow commented Feb 3, 2026

@bobbrow Were all your concerns addressed?

I haven't had the time to go through very many files yet.

Copy link

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

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


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

bobbrow
bobbrow previously approved these changes Feb 4, 2026
Copy link
Member

@bobbrow bobbrow left a comment

Choose a reason for hiding this comment

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

I left one optional comment

// clients, so the native process is already aware of all workspace
// folders before receiving new CppProperties for new folders.
this.defaultClient.sendDidChangeSettings();
await this.defaultClient.sendDidChangeSettings();
Copy link
Contributor

Choose a reason for hiding this comment

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

It might have been intentional that there was no await here. An await would allow other things to happen in parallel, potentially allowing other LSP messages through before the call to createClient a few lines down. I don't think awaiting sendDidChangeSettings is required. It's sending a notification as soon as ready. It might be safest to preserve the original behavior and use void instead of await.

Copy link
Contributor Author

@sean-mcmanus sean-mcmanus Feb 5, 2026

Choose a reason for hiding this comment

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

Sure, I can change it back to void, but comment makes it sound like it expected the settings to be send before hand though: send them up before creating new clients.

const mappingString: string = baseFileName + "@" + document.fileName;
client.addFileAssociations(mappingString, "cpp");
client.sendDidChangeSettings();
await client.sendDidChangeSettings();
Copy link
Contributor

Choose a reason for hiding this comment

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

This should not be awaited here. In the protocol handler, a call to await can results in other messages being processed, resulting in messages out of order (i.e. file-related requests before the didOpen is processed).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I did that because otherwise it seemed like the setTextDocumentLanguage could happen after the sendDidChangeSettings, but I can change it back to void.

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

Labels

None yet

Projects

Status: Pull Request

Development

Successfully merging this pull request may close these issues.

3 participants