secondlife / secondlife/sl-vscode-plugin
Luau language server highlighting does not work with scripts in the SL object explorer
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 15
- Avg merge
- 14h 50m
- Merged PRs (30d)
- 9
Description
Description:
Features of the language server (autocomplete hints, hover doc strings, deprecated function strikethrough, etc.) do not work with luau files that are viewed from the plugin's object view.
Steps to reproduce:
- Install the Second Live VS code plugin
- Install the Luau language server
- Start second life and connect with the plugin
- Create a .luau file in your VS Code workspace
- Copy the following script into it:
function LLEvents.touch(events)
ll.Say(0, "I've been touched!")
end
ll.Cloud(ZERO_VECTOR)
- Note that if you hover over a function you see docstrings popup
- Note that ll.Cloud is crossed out because it is deprecated.
- Start typing "ll." and Note that autocompletions are suggested.
- Go to Second life and create a new Object with a new script and start exploring in VS code
- Copy the script from step 5 to the script in the object.
- Repeat steps 6 - 8 with the script in the second life object
Result:
None of the functionality works on the script from the second life object.
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
No files or tests are named. Reproduce the issue using the listed Second Life object-view steps, then trace how object-view Luau documents are opened and connected to the language server compared with workspace files. Done means hover documentation, deprecated-function highlighting, and autocomplete work for scripts viewed from the object explorer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100