Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Warnings in war3map.j
See original GitHub issueWurst reports errors in the auto-generated war3map.j file:
Is this intentional? If so, it would be a nice to be able to disable warnings in said file.
A Little Bit of Context
I’m defining some global variables (the udg_* stuff) in the map file (e.g., regions and names of said regions) that I want to use in my Wurst code. These global variables are neatly extracted into the war3map.j file when Wurst is run. Since war3map.j is merely extracted, I don’t think that Wurst should report warnings in it. I have no control over the war3map.j code generation.
Side issue: It would be nice to have something like @extern for global variables that are not defined in .wurst files but defined in e.g. war3map.j (all the udg_* variables). Imagine a freshly cloned repo that doesn’t have war3map.j. In said repo, the udg_* variables do not exist yet. Therefore, Wurst won’t run since all the references to udg_* variables can’t be resolved. I have to manually extract the war3map.j file first. This is annoying.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
hm yeah, that was yet another warning.
@Frotty Thanks for looking into this issue. Unfortunately, the warnings persist even after your latest commit:
Have I missed something?