Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug Report: Issues with nested tables with named keys #211

Open
Connor-McCloskey opened this issue May 9, 2024 · 0 comments
Open

Bug Report: Issues with nested tables with named keys #211

Connor-McCloskey opened this issue May 9, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Connor-McCloskey
Copy link

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.

@Connor-McCloskey Connor-McCloskey added the bug Something isn't working label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant