microsoft / microsoft/TypeScript
Find all references across project references
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Bug Report
🔎 Search Terms
references
find all references
rename
🕗 Version & Regression Information
⏯ Playground Link
💻 Code
These are more scenarios from investigations of #42976 where the definition is considered local but is exported and can be referenced by other projects. So we need to think about a way to figure that out efficiently.
/// /shared/src/index.ts
const local = class {
foo: string;
constructor() {
this.foo = "foo";
}
fly() {
console.log(this.foo);
}
};
export const d = local;
class xy {
foo: string;
constructor() {
this.foo = "foo";
}
fly() {
console.log(this.foo);
}
};
export { xy };
🙁 Actual behavior
fly usage from project referencing the shared does not load other projects
🙂 Expected behavior
fly usage from project referencing the shared should load other projects
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 by reproducing the project-reference scenario shown in the issue, using the shared/index.ts example and a referencing project. Compare find-all-references behavior for the exported local class and exported xy class; the fix is complete when fly usage from the referencing project loads references from other projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100