The folder association linking is currently broken in v1.0.3, it was working in v1.0.2
I confirmed this bug:
- I did a live test of it working in the previous version,
- updated it and then
- it wasn't able to find it anymore.
The notification popup says "No master script found for: testfoo.luau" -- the script name is named test/foo in-world and there is a folder with test/foo.luau, note the lack of separators in the notification.
For anyone coming around to this issue, there are two workarounds:
- Use the new
--@file syntax, but you need to enable it in the settings (slVscodeEdit.sync.useFileMetaForMatching)
- Drop back to v1.0.2 to use nested folders
Note for using --@file:
- specify the directory and file name (
.luau optional), e.g. --@file test/foo.luau worked for me,
- Add the
--@file line at top of the in-world script (even if it's just the hello world example) and in your vscode file,
- Press
Edit...
Also turn on slVscodeEdit.sync.includeFileMetaInOutput, so that it will keep the --@file comment saved into the in-world script, which avoids it getting lost when you open it up again.
The folder association linking is currently broken in v1.0.3, it was working in v1.0.2
I confirmed this bug:
The notification popup says "No master script found for: testfoo.luau" -- the script name is named
test/fooin-world and there is a folder withtest/foo.luau, note the lack of separators in the notification.For anyone coming around to this issue, there are two workarounds:
--@filesyntax, but you need to enable it in the settings (slVscodeEdit.sync.useFileMetaForMatching)Note for using
--@file:.luauoptional), e.g.--@file test/foo.luauworked for me,--@fileline at top of the in-world script (even if it's just the hello world example) and in your vscode file,Edit...Also turn on
slVscodeEdit.sync.includeFileMetaInOutput, so that it will keep the--@filecomment saved into the in-world script, which avoids it getting lost when you open it up again.