LuaLS / LuaLS/lua-language-server

适应Unity插件

Open
#2,306 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
4.4k
Forks
442
PR merge metrics
No merged PRs in 30d

Description

### How are you using the lua-language-server?

Visual Studio Code Extension (sumneko.lua)

### Which OS are you using?

Windows

### What is the issue affecting?

Annotations, Type Checking, Completion

### Expected Behaviour

对emmylua-unity插件的支持还有比较多的bug, 首先导出时
![image](https://github.com/LuaLS/lua-language-server/assets/40318218/73e5cabf-070b-4827-bce3-6cbe5e710c91)
没有处理可空参数, 这个是我后面加的, 可能需要支持下.

![image](https://github.com/LuaLS/lua-language-server/assets/40318218/449f0020-06ef-45be-81c2-5d8448c37342)
有些api的导出较大, 不知道是否会影响提示

![image](https://github.com/LuaLS/lua-language-server/assets/40318218/93fac382-f29e-4ebc-9cb6-0f050d5ad5d8)
CS的field依然不完整, 不知道是哪个版本以来的BUG

### Actual Behaviour

### Reproduction steps

### Additional Notes

### Log File

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the emmylua-unity integration problems in the Visual Studio Code extension on Windows, focusing on nullable parameters during export, large API exports, and incomplete C# fields. The issue names no source files, tests, or reproduction steps, so identify the relevant export and completion entry points before defining tests and confirming the expected Unity API output.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, unity
Domain
game-dev, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.