All references are not being found for module component

[aspeddro]

ApiLayout.res on ReScript lang website.

The analysis return two locations:

dune exec rescript-editor-analysis references ~/Desktop/projects/rescript-lang.org/src/layouts/ApiLayout.res 130 9

[ 
{"uri": "file:///home/pedro/Desktop/projects/rescript-lang.org/src/layouts/SidebarLayout.res", "range": {"start": {"line": 209, "character": 4}, "end": {"line": 209, "character": 8}}},
{"uri": "file:///home/pedro/Desktop/projects/rescript-lang.org/src/layouts/SidebarLayout.resi", "range": {"start": {"line": 64, "character": 4}, "end": {"line": 64, "character": 8}}}
]

The locations above are of make function, i.e, definition.

The real references occur in other files:

• DocsLayout.res
• ApiLayout.res (the current file)

[cristianoc]

As a simpler example:

module M1 = {
  let x1 = 10

  @react.component
  let make = () => React.null
}

module M2 = {
  let x2 = 10
}

No references are found for x1 (not even its own definition) while they are found for x2.
So it seems that by just being in the same module as a component breaks references.

[cristianoc]

Even simpler example:

module M1 = {
  let x = 10

  let a = 3
  let a = a
}

module M2 = {
  let x = 10
}

[cristianoc]

This could be relevant: #622
At least, same scenario of shadowing triggering the observed issue.

[cristianoc]

So shadowing creates a module constraint (i.e. a module type generated by the compiler), but also an example with an explicit module type has the same problem:

module M3: {
  let aa: int
} = {
  let aa = 13
}

let dd = M3.aa
//           ^ref

[cristianoc]

@aspeddro this should be fixed in #646

[aspeddro]

I just tested #646 and the references still point to definition.

[cristianoc]

Seems to work on the project used to test the extension. Might need a separate small repro.