Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getDocumentHighlights does not return uses of SFCs in JSX elements #7109

Closed
myitcv opened this issue Feb 17, 2016 · 4 comments
Closed

getDocumentHighlights does not return uses of SFCs in JSX elements #7109

myitcv opened this issue Feb 17, 2016 · 4 comments
Assignees
Labels
Bug A bug in TypeScript Domain: JSX/TSX Relates to the JSX parser and emitter Fixed A PR has been merged for this issue

Comments

@myitcv
Copy link

myitcv commented Feb 17, 2016

This issue first surfaced in palantir/tslint#972

I think the following is a minimal reproduction of the problem:

/// <reference path='fourslash.ts' />

//@Filename: file.tsx
//// export function BuildMyComponent(): JSX.Element {
////    let [|StringComponentA|]: React.ComponentClass<{}>;
////    return <[|StringCom/**/ponentA|] />;
//// }

The issue first surfaced in 1.9.0-dev.20160212; indeed I think I've bisected the problem to 13167f5 using the above test

@myitcv
Copy link
Author

myitcv commented Feb 29, 2016

@mhegazy @RyanCavanaugh - anyone using tslint with the no-unused-variable rule (and React) is currently blocked from upgrading past 1.9.0-dev.20160212 (details palantir/tslint#972) because of this issue.

Is there any chance therefore that this could be addressed before the 2.0 milestone?

That would then allow us to pick up and test things like private constructors which landed in more recent nightlies.

Thanks in advance

@RyanCavanaugh
Copy link
Member

We'd take a PR at any time but I have other more urgent work at the moment. It'll probably be a week or two before I get to this.

@myitcv
Copy link
Author

myitcv commented Mar 2, 2016

Thanks Ryan
On 29 Feb 2016 21:29, "Ryan Cavanaugh" notifications@github.com wrote:

We'd take a PR at any time but I have other more urgent work at the
moment. It'll probably be a week or two before I get to this.


Reply to this email directly or view it on GitHub
#7109 (comment)
.

@myitcv
Copy link
Author

myitcv commented Mar 22, 2016

Confirmed this is fixed by #7622 (thanks @mhegazy) available as of 1.9.0-dev.20160322

@myitcv myitcv closed this as completed Mar 22, 2016
@mhegazy mhegazy added the Fixed A PR has been merged for this issue label Mar 22, 2016
@DanielRosenwasser DanielRosenwasser added the Domain: JSX/TSX Relates to the JSX parser and emitter label Mar 22, 2016
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug A bug in TypeScript Domain: JSX/TSX Relates to the JSX parser and emitter Fixed A PR has been merged for this issue
Projects
None yet
Development

No branches or pull requests

4 participants