addon validation

[sirinsidiator]

There are many things that would be interesting to validate when creating a release build.

• Manifest file for missing directives (author, addon version, api version, etc) or incorrect information (typos, non-existing files, unused lua/xml files in the addon folder)
• Static code analysis of lua and xml files via SonarQube
• xml schema validation.
• Addon Dependencies (check if there are newer versions than last time that should be reviewed)
• Leaked globals (there is already a tool, but it uses powershell which limits it to windows)
• Use of removed APIs after an update (could make use of esoui-doc-converter).

[haggen]

I would be against baking integration with proprietary/cloud solutions like the SonarQube into the tool. At most expose some information like paths and whatnot so you can make your own integration. I would rather use open source tools like mpeterv/luacheck and xmllint from libxml (which already has bindings for node in npm).

[sirinsidiator]

If I am not completely mistaken, SonarQube is free open source software and runs locally? You can check out their code here. I use the eclipse plugin myself which is really nice.