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

Error when running genEmmyAPI #10

Open
emiliakaida opened this issue Dec 31, 2020 · 5 comments
Open

Error when running genEmmyAPI #10

emiliakaida opened this issue Dec 31, 2020 · 5 comments

Comments

@emiliakaida
Copy link

emiliakaida commented Dec 31, 2020

I encountered this error message when issuing the command "lua genEmmyAPI.lua":

lua: genEmmyAPI.lua:118: attempt to concatenate a nil value (field 'name')
stack traceback:
        genEmmyAPI.lua:118: in upvalue 'genModule'
        genEmmyAPI.lua:136: in local 'genModule'
        genEmmyAPI.lua:149: in main chunk
        [C]: in ?

although I followed exactly the steps in the README.
I'm currently on Windows 10 64bit.
Do you have any idea how to fix this?
Thanks in advance.

@emiliakaida emiliakaida changed the title Error when genEmmyLua Error when running genEmmyAPI Dec 31, 2020
@ISTAnsver
Copy link

Seems I've found a reason. But while I don't know how to fix it.
It relates to module types. For example take Audio module. There're 2 types. But when script is running there're 3 types:

  • the table from RecordingDevice.lua
  • the table from Source.lua
  • .\modules\audio\types\Source.lua (just a string — path to Source.lua)

I don't know how .\modules\audio\types\Source.lua has appeared there but it's strange.

@michaelslec
Copy link

michaelslec commented Mar 29, 2021

I'm still having this issue. Any progress?

@ImpleLee
Copy link

Maybe you can try #12? But #12 is more specific to the Lua language server on VS Code, so maybe the generated code is less useful for other EmmyLua plugins...

@igorr0driguez
Copy link

igorr0driguez commented Jan 20, 2023

Issue still happening in W11 64bit.

The thing is that the API has evolved while the script has not.

Unfortunately I'm not able to fix that right now, otherwise would be already working on that.

@Ahri-Spica
Copy link

hope you can find the time at some point

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants