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
I'm currently rewriting my love-atom package to work with atom-autocomplete-lua and I've run into a small into issue with the return types of function variants.
Below is an example of how my JSON file is formatted:
In this case (local foo = love.graphics.newText()), foo is correctly marked as an object of type Text.
As far as I know there are some functions in the LÖVE API whose variants have different returnTypes so I can't simply move them outside of the variant definition.
Is there something I am missing, or is this not supported by your package?
Best wishes, Robert
The text was updated successfully, but these errors were encountered:
Yup. This is not currently supported by this package. But this would be an interesting feature to have. I'll leave this issue open and maybe look into it at some point.
rm-code
added a commit
to rm-code/love-atom
that referenced
this issue
Apr 30, 2017
Currently atom-autocomplete-lua doesn't support the definition of
returnTypes inside of function variants which caused the autocompletion
for some variables to fail.
This commit is a workaround until the issue has been resolved.
@seedapetcu21/atom-autocomplete-lua#15Closes#9.
Hi @dapetcu21,
I'm currently rewriting my love-atom package to work with atom-autocomplete-lua and I've run into a small into issue with the return types of function variants.
Below is an example of how my JSON file is formatted:
As you can see the
returnTypes
are inside of the variants table and atom-autocomplete-lua doesn't resolve them correctly.When I write
local foo = love.graphics.newImageData()
,foo
doesn't have any method suggestions.It works fine for functions without variants:
In this case (
local foo = love.graphics.newText()
),foo
is correctly marked as an object of typeText
.As far as I know there are some functions in the LÖVE API whose variants have different
returnTypes
so I can't simply move them outside of the variant definition.Is there something I am missing, or is this not supported by your package?
Best wishes, Robert
The text was updated successfully, but these errors were encountered: