Skip to content

Allow intersections with string literal, number literal, or unique symbols to be used as property names#61147

Closed
chkn wants to merge 1 commit intomicrosoft:mainfrom
chkn:fix-61093
Closed

Allow intersections with string literal, number literal, or unique symbols to be used as property names#61147
chkn wants to merge 1 commit intomicrosoft:mainfrom
chkn:fix-61093

Conversation

@chkn
Copy link
Copy Markdown

@chkn chkn commented Feb 7, 2025

Fixes #61093

In addition to string literals, number literals, and unique symbols, this allows intersections with those types to also be used as property names.

@chkn
Copy link
Copy Markdown
Author

chkn commented Feb 7, 2025

@microsoft-github-policy-service agree

@typescript-bot
Copy link
Copy Markdown
Collaborator

With 6.0 out as the final release vehicle for this codebase, we're closing all PRs that don't fit the merge criteria for post-6.0 patches. If you think this was a mistake and this PR fits the post-6.0 patch criteria, please post to the 6.0 iteration issue with details (specifically, which PR and which patch criteria it satisfies).

Next steps for PRs:

  • For crash bugfixes or language service improvements, PRs are currently accepted at the typescript-go repo
  • Changes to type system behavior should wait until after 7.0, at which point mainline TypeScript development will resume in this repository with the Go codebase
  • Library file updates (lib.d.ts etc) continue to live in this repo or the DOM Generator repo as appropriate

@github-project-automation github-project-automation bot moved this from Not started to Done in PR Backlog Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Branded literal type widened in unexpected way

3 participants