You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
There's something funky going on with passing tables with nested tables that have named key/value pairs back to GDScript. When doing so, you'll receive this error: bad argument #1 to 'base.next' (table expected, got function)
To Reproduce
Pass a table such as this one described here from any Lua function to a function in GDScript:
local nested = {x=1,y=2}
local t = {}
table.insert(t, nested)
godot_test_function(t)
Expected behavior
I would expect GDScript to just receive a dictionary or array as normal.
The text was updated successfully, but these errors were encountered:
Describe the bug
There's something funky going on with passing tables with nested tables that have named key/value pairs back to GDScript. When doing so, you'll receive this error: bad argument #1 to 'base.next' (table expected, got function)
To Reproduce
Pass a table such as this one described here from any Lua function to a function in GDScript:
local nested = {x=1,y=2}
local t = {}
table.insert(t, nested)
godot_test_function(t)
Expected behavior
I would expect GDScript to just receive a dictionary or array as normal.
The text was updated successfully, but these errors were encountered: