You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Either we state an id is only unique per kind which will probably confuse people, or we extend the id.
The simplest thing would probably be to additionaly include kind in the id: <kind>.<modulePath>.<itemName>.
For the above examples:
type.Example.x / value.Example.x
moduleType.Example.M / module.Example.M
type.Example.M.x / value.Example.M.x
P.S: If above seems appropriate, I think I'd be able to send a PR to implement this:
I'd adapt the makeId function:
The way docgen currently calculates the
id
is ambiguous ifThis defeats the purpose of having a (supposedly unique) id.
Value / Type Example
generates
Module (Type) Example
generates
Proposal
Either we state an id is only unique per
kind
which will probably confuse people, or we extend the id.The simplest thing would probably be to additionaly include
kind
in the id:<kind>.<modulePath>.<itemName>
.For the above examples:
type.Example.x
/value.Example.x
moduleType.Example.M
/module.Example.M
type.Example.M.x
/value.Example.M.x
P.S: If above seems appropriate, I think I'd be able to send a PR to implement this:
I'd adapt the
makeId
function:rescript-vscode/tools/src/tools.ml
Lines 301 to 302 in a6108b3
to take an additional optional labeled argument
prefix
and call it accordingly.The text was updated successfully, but these errors were encountered: