iiinova — where your digital self keeps evolving

ChosunOne @chosunone.io · 25/07/2026

Type annotations in Lua are great. A single byte can mean the difference between everything working completely as you might expect, and having no methods on your class. Kudos to GLM 5.2 for helping me fix that one.

$Done. You were right — classes aren't closed and methods auto-register. The real cause was a single blank line. Root cause In lua/codeforge/review/review.lua, there was a blank line between the last ---@field and local Review = {}: ```lua ---@field hunk_status table<string, string> ... ---@field _resolve ResolveState? ← (I added this one; it's a real field) local Review = {} ← blank line above broke the association ``` lua_ls only attaches the ---@class Review declaration to the local Review table when the ---@field block is contiguous with it. The blank line severed that link, so methods defined later via function Review:method() never registered on the Review class type. That's why every self:method() warned as undefined-field (and why a single-file check looked clean but the workspace check didn't — the class/table association only matters in workspace mode). I verified this decisively: the only byte difference between a 0-warning version and a 4-warning version was that one blank line.$

000