Skip to content

Conversation

@sheetalkamat
Copy link
Member

No description provided.

@sheetalkamat sheetalkamat force-pushed the multiProject branch 5 times, most recently from 46a8abe to f66df9c Compare November 3, 2025 20:32
@sheetalkamat sheetalkamat marked this pull request as ready for review November 4, 2025 20:00
Copilot AI review requested due to automatic review settings November 4, 2025 20:00
Copy link
Contributor

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 updates test baselines to reflect improved formatting and line numbering consistency in the test output files. The changes normalize how JSON content and TypeScript code are displayed in baseline files, removing inconsistent indentation and adding proper line numbers to all content.

Key Changes

  • Standardized line numbering for all file content in test baselines
  • Normalized JSON formatting to use consistent indentation (4 spaces)
  • Fixed indentation for TypeScript code blocks in test files
  • Updated hash values in tsbuildinfo files to reflect the normalized content

Reviewed Changes

Copilot reviewed 100 out of 125 changed files in this pull request and generated 62 comments.

Show a summary per file
File Description
tsc/moduleResolution/alternateResult.js Added line numbers to JSON package files and normalized their indentation
tsc/declarationEmit/when-using-Windows-paths-and-uppercase-letters.js Standardized indentation for TypeScript source code and adjusted error column positions
tsbuildWatch/projectsBuilding/*.js Normalized tsconfig.json indentation across multiple project building tests
tsbuildWatch/programUpdates/*.js Updated file content formatting and corresponding hash values in tsbuildinfo
tsbuild/resolveJsonModule/*.js Consistent JSON formatting for all tsconfig.json files
lspservertests/rename/*.js Added complete baseline content for new rename test cases
lspservertests/findAllRefs/*.js Added complete baseline content for new find all references test cases

Copy link
Member

@jakebailey jakebailey left a comment

Choose a reason for hiding this comment

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

Some comments; have not read the entire thing yet.

@sheetalkamat
Copy link
Member Author

converting tests to fourslash uncovered some more ordering issues with results. Looking into that as well as handling the feedback

Copy link
Member

@andrewbranch andrewbranch left a comment

Choose a reason for hiding this comment

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

All my concerns are addressed, hopefully someone else can review as well 👍

@jakebailey
Copy link
Member

I'll give it another pass shortly, though I was waiting until it was mostly passing CI.

let testOutput: string;
try {
testOutput = cp.execFileSync(go, ["test", "./internal/fourslash/tests/gen"], { encoding: "utf-8" });
testOutput = cp.execFileSync(go, ["test", "-v", "./internal/fourslash/tests/gen"], { encoding: "utf-8" });
Copy link
Member

Choose a reason for hiding this comment

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

Does this end up printing a lot?

Copy link
Member Author

Choose a reason for hiding this comment

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

This is when it panics we can diagnose the issue rather than having to manually run those steps and tests again to figure out which test had panic that was not expected. (eg i got one when i was not associating reqID for panics when operating on projects inside those go routines.)

@sheetalkamat
Copy link
Member Author

All my concerns are addressed, hopefully someone else can review as well 👍

I am still looking into deduplicating results as there is still something going on there.

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