Is this a feature or a bug: If you use `cfparam` ...
# adobe
n
Is this a feature or a bug: If you use
cfparam
in CF2021 where
name
is a key in a struct that doesn't exist, it creates it. But in CF2023, it breaks. This is creating a double-nested key (i.e. a key in a struct in a struct), but it happens even at 1 level deep: https://trycf.com/gist/022e3569d45b53298539806099d5dba3/acf2021?theme=monokai
d
There's something the matter with trycf, just submitting it with no code throws the same error.
At first I thought it was that it didn't like the struct literal with { } on line 1, and it's true that just that one line throws the same error, but with no code at all, that seems like a site issue.
n
Gah... I should've double-checked. You're right.
Thanks!
d
Sure, weird. Everything works until it's broken.
💯 1
🤣 1
a
@abram ^^^
👍 1
d
Leaving aside the 2023 trycf problem, the 2021 result is exactly what I'd expect. @Nick, are you good with that?
n
Yes, that's what I'd expect too
👍 1
a
Sorry all, my slack install hosed and I didn't see the notification. Had to manually delete registry keys to get slack to reinstall 😞. CF 2023 is back up on trycf.
🎉 1
👍 2
1