Skip to content

Accepted symbol baselines#4007

Open
RyanCavanaugh wants to merge 3 commits into
microsoft:mainfrom
RyanCavanaugh:acceptedSymbols
Open

Accepted symbol baselines#4007
RyanCavanaugh wants to merge 3 commits into
microsoft:mainfrom
RyanCavanaugh:acceptedSymbols

Conversation

@RyanCavanaugh
Copy link
Copy Markdown
Member

Bugs / investigation sections to come in a later PR

Copilot AI review requested due to automatic review settings May 20, 2026 18:18
Copy link
Copy Markdown
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.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

compiler/nodeNextCjsNamespaceImportDefault1.symbols.diff
compiler/nodeNextCjsNamespaceImportDefault2.symbols.diff

# Declaration position `(file, --, --)` changed to actual numeric positions
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

(file, --, --) is sanitized lib refs so changes to lib positions don't affect baselines - are these missing lib bindings, or are we failing to sanitize? Both seem bad.


# `.constructor` property access now resolves to `Object.constructor` from lib
## Accessing `.constructor` on a class type now correctly resolves to the inherited `Object.constructor` symbol
conformance/typesWithPrivateConstructor.symbols.diff
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

In strada we filtered these from the .symbol output - why?

conformance/typesWithProtectedConstructor.symbols.diff

# Import specifier in re-exports resolves to alias target symbol name
## In `import { x as y }`, the symbol for `x` now reports as the target name `y`. Either is arguably correct.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

All of these "we're using the local name for the thing instead of the target's globally accessible/local name" things all track back to possible diffs in name lookup behavior. The new behavior seems "better" since it respects locals more, though figuring out why there's a diff might be informative.

conformance/nodeModulesSynchronousCallErrors(module=nodenext).symbols.diff

# Test baseline reduction (removed extra file outputs)
## This test has an error, fix later.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Uh, doesn't this mean it should be in the to-triage set, not "accepted"?


# Additional Decl entries for multi-declaration function symbols
## `flatMap` function with multiple declarations now shows all Decl entries on the symbol
conformance/templateInsideCallback.symbols.diff
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This just belongs in the @overload JSDoc tags now contribute Decl entries to the host function/method symbol group.

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.

3 participants