Sometimes when you export types in a module or values with types, the types wont be exported and the value will be *error-type*.
Started happening after this crappy UI Update.
(Same issue in New type solver)
As I wrote this little example below, right after constructing the World, hovering over it, it says any this time, 15 secs later it was fine BugReport.rbxl (81.4 KB)
(Hovering over World sometimes will say error-type, not guaranteed)
It doesn’t matter what the code is, code isn’t the problem, it’s the script editor bugging out and not importing types or not setting types of a variable.
local Jecs = require(Packages.jecs) --// clearly returns API and exports types
local World = Jecs.world() --// Hovering over World will SOMETIMES say *error-type*
yea not just you, some scripts Ive had with intelisense working before have stopped prompting autocomplete for the module itself as well as the handlers/metatables returned, tried a few things out including passing the type on the modules return, the fact that the module itelf isnt prompting intelisense tho is telling me somethings up as it should at a minimum be prompting the module scripts functions as it does that by default
Edit:
Already have it uploaded as a backup while i took a break from working on it(Should be up to date)
This contains numerous handlers for things that had intelisense working before Game Ready Modules - Creator Store
fairly sure ^ should still replicate the issues ive had, not extremely into typechecking so i kept it simple.
pretty sure it has to do with the incremental typechecker which was pushed out as the default. There’s probably some more unironed bugs in there. The old typechecker didn’t try to cache much and was always reliable. The new system is probably caching too aggressively and not updating the exported types