Release Notes for 672

Updates Release Notes
35

This update has broken a lot of the typechecker autofill annotations for me. I do not use strict typechecking, but I use some annotations to get the autofill working. Because of that, my type annotations are obviously incorrect and would raise a bunch of strict typechecking errors, but i don’t have strict turned on, but up until recently, the autofill would still work at least

--example of what broke

type entry = {
    property1: boolean,
    thing2: CFrame,
    num: number,
}

local list :{entry} = {}

list[1] = {
    --when i start typing "p..." here property1 autofills
    thing2 --this never autofills, seems to break for any non-boolean values
    --num also never autofills
}

i can still get the autofill to work but not in that clean “construct and fill” table way, instead i gotta restate the thing a gazillion times

list[1] = {}
list[1].property1 = false
list[1].thing2 = CFrame.new()
list[1].num = 5

--OR
local thingy = {} ::entry
thingy.property1 = false
...
list[1] = thingy

both of these are so much uglier than just doing the “fill construct”

EDIT: i have no clue whats going on
the root of the problem doesnt seem to be the types being booleans or not booleans, for some reason some certain string keys cause the typechecker to blow up, cant seem to find a pattern
for some reason string keys like
“ItemId” autofill, “DmgReductionRatio”, “IsArmor”, work
ones that break it are “Added”??

1 Like