luau-lang/rfcs
1
0
Fork 0
mirror of https://github.com/luau-lang/rfcs.git synced 2025-05-04 10:43:48 +01:00
Code Issues Projects Releases Packages Wiki Activity

Link old implementations to these approaches

Browse source
This commit is contained in:
Varun Saini 2024-09-12 11:38:07 -07:00
parent 641d97e6a0
commit 86e531e3a5
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/amended-alias-resolution.md
View file

@ -12,10 +12,12 @@ In an [old RFC for require-by-string](https://github.com/luau-lang/luau/pull/969
the path `require("my/module")` is resolved by first checking if `my` is an alias defined in a `.luaurc` file. the path `require("my/module")` is resolved by first checking if `my` is an alias defined in a `.luaurc` file.
If so, we perform a string substitution on `my`. If so, we perform a string substitution on `my`.
If not, we try to resolve `my/module` relative to the requiring file. If not, we try to resolve `my/module` relative to the requiring file.
This is identical to approach (3a) below.
This design changed in the next few months and became what we now have in [require-by-string-aliases.md](require-by-string-aliases.md): This design changed in the next few months and became what we now have in [require-by-string-aliases.md](require-by-string-aliases.md):
when requiring an alias, it must be prepended with the `@` prefix. when requiring an alias, it must be prepended with the `@` prefix.
Otherwise, we will assume the given string does not contain an alias and will resolve it relative to the requiring file. Otherwise, we will assume the given string does not contain an alias and will resolve it relative to the requiring file.
This is identical to approach (1a) below.
There have been disagreements about which approach is more appropriate, so this RFC will serve as a way to document the ongoing discussion and the final decision we make. There have been disagreements about which approach is more appropriate, so this RFC will serve as a way to document the ongoing discussion and the final decision we make.