secondlife / secondlife/sl-vscode-plugin
Folder association is broken
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 15
- Avg merge
- 14h 50m
- Merged PRs (30d)
- 9
Description
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
--@filesyntax, 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 (
.luauoptional), e.g.--@file test/foo.luauworked for me, - Add the
--@fileline 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the regression by comparing folder association in v1.0.3 with v1.0.2 for an in-world script named test/foo and a file named test/foo.luau. Inspect the folder-matching path and the --@file workaround settings, then verify that nested folders resolve without the missing-separator notification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100