Skip to content

Go-to-definition fails for a use of a provided constructor #5538

Description

@cartermp
  1. Install FSharp.Data (3.0.0-beta4 is what I tested with)
  2. Add the following code:
open FSharp.Data

type MyCSV = CsvProvider<"1, 2, 3, 4, 5">

// Go to definition on 'MyCSV' works here.
let sample = MyCSV.GetSample()

// Go to definition on 'MyCSV' does not work here.
let noWorky = MyCSV()

Note that in the first case, Go to Definition succeeds. In fact, it seems to succeed in all cases aside from the noWorky sample. Note that semantic highlighting does not pick up the declaration of MyCSV in the latter case, probably indicating that something is not getting resolved correctly in name resolution.

image

This is not a regression as far as we can tell, at least not with any previous VS 2017 release.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-LangService-Navigationgo to definition, F1 help + the FCS APIs related to itBugImpact-Low(Internal MS Team use only) Describes an issue with limited impact on existing code.

    Type

    No fields configured for Bug.

    Projects

    Status
    New

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions