microsoft / microsoft/TypeScript
Annotations/IntelliSense gets lost with simple `&` and `|` joins or utilities
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
🔎 Search Terms
IntelliSense, comments, annotations, symbol annotation, utilities, utility, union, intersection
🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about annotations
⏯ Playground Link
💻 Code
// follow Playground link to see behavior
export interface Foo {
/** An annotation for first property */
firstProperty: boolean
/** An annotation for second property */
secondProperty: number
}
export interface Bar {
/** An annotation for the third property */
thirdProperty: string
}
const foo: Foo = {
// roll over to get annotation
firstProperty: false,
// roll over to get annotation
secondProperty: 42
}
export type FooAndOrBar = (Foo & Bar) | Foo | Bar
const fooAndBar: FooAndOrBar = {
// rollover annotations don't work here
firstProperty: true,
secondProperty: 2,
thirdProperty: "hello"
}
🙁 Actual behavior
IntelliSense doesn't work on properties after running through & (intersections) with | (unions) or more complex type manipulation.
🙂 Expected behavior
I expected the annotation to "come along" with the symbol and appear in IntelliSense.
Additional information about the issue
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked TypeScript Playground reproduction and compare property IntelliSense for Foo, Bar, and FooAndOrBar. Trace how annotations are preserved through the intersection and union types, then verify that rollover IntelliSense shows the expected annotations for all three properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100