Autocomplete does not take escaped identifiers into account

[cknitt]

E.g.

module X = {
  let \"Foo" = "foo"
}

let x = X.

completes to X.Foo instead of X.\"Foo".

[cristianoc]

It would be nice to move in the opposite direction, even though it's not so obvious how exactly to do that.
There are cases where upper case ids, or non-standard ids, are necessary, such as for components.

Wondering whether there is a way to legitimise the legitimate use cases without the free-for-all quoted thing which is really not recommended unless there's no other way.

[cristianoc]

For example, this

let foo = (x,y) => x+y

does two things: it defines an anonymous function, and binds it to variable foo.
One could imagine some mechanism to specify the name of the function seen by console.log(foo.name).

[cknitt]

This affects hover, too, not just completion.

Hovering on the above module X incorrectly shows

module X = {
  let Foo: string
}

Escaped identifiers also occur for prop names in both the React Native and the Material-UI bindings, e.g.

<Mui.Dialog \"open"=true>
  ...

or

<FlatList
  \"ItemSeparatorComponent"={_ => <Separator />}
  ...

where they are not completed correctly either.