debugChicken

Results 24 comments of debugChicken

yes it worked. my window, for reference: ![image](https://user-images.githubusercontent.com/30127664/223502874-3284532c-25c3-4f75-8f9a-c6dac9c0e089.png) my window, on the probes: ![image](https://user-images.githubusercontent.com/30127664/223503004-5ba0df90-e593-4ced-a21c-c6a46df4fcc4.png) ![image](https://user-images.githubusercontent.com/30127664/223503133-b529176a-b3b6-4f4c-8b51-a66865debb95.png)

exactly my thoughts :| its not as useful if you can just make a typo / change values and not be warned about it

yes. Its kinda pointless to have enum if no errors are thrown when you use invalid values i'm having to use a class instead ``` ---@class sfxChar ---@field jump string...

> duplicate of #2384 > > And as I commented there:[#2384 (comment)](https://github.com/LuaLS/lua-language-server/issues/2384#issuecomment-2198052928), `undefined-field` diagnostics only check for typed tables (for performance reason I guess), but the **enum binded table** are...

``` ---@enum (.*) (.*)\{ ---@enum $1.* $2{ ---@class $1 ``` if anyone wants to replace

> Actually you don't need to follow my annotation practice exactly 😂 (I mean the TestEnum`.*`) > You can keep you enum type name as `TestEnum`, then name the underlying...

> @sumneko please fix @sumneko is quite the character - makes an amazing tool with just a simple missing feature - refuses to elaborate - leaves gigachad

> Like many of us, the author has a full time job. 😅 The amazing thing about open source projects is that **contributions are welcome**, and maybe we can fix...