[implemented] api version variable in addon manifest

[sirinsidiator]

I was just wondering if it would be possible to add a new variable for the addon manifest so that we can make the addon compatible for both api versions on a major patch without having to clutter the code with

if(GetAPIVersion() == 100011) then 
--old 
else 
--new 
end

Something like

Startup_${apiversion}.lua

which then loads either Startup_100011.lua or Startup_100012.lua depending on the api version.

[Fyrakin]

Originally Posted by sirinsidiator I was just wondering if it would be possible to add a new variable for the addon manifest so that we can make the addon compatible for both api versions on a major patch without having to clutter the code with if(GetAPIVersion() == 100011) then --old else --new end Something like Startup_${apiversion}.lua which then loads either Startup_100011.lua or Startup_100012.lua depending on the api version.

Well, api version never goes backwards on live, you would have to remove the redundant file with the next add-on update anyway. I see no problems having add-on tested and prepared on PTS and updated once patch went live.

[sirinsidiator]

Of course you will remove the old version once it is no longer necessary, but there is also the delay in the update between EU and NA server to think about. That way you could easily upload a version that is compatible with both APIs and make the transition as smooth as can be.
Also it can't hurt to have the addon ready and published for the PTS so people can test your changes beforehand and instead of making a separate addon I would prefer to just have a version that is compatible with both.

Even without this feature I will find a way to do it, but it would be much cleaner this way, because no unnecessary code is loaded.

[Randactyl]

Originally Posted by sirinsidiator Also it can't hurt to have the addon ready and published for the PTS so people can test your changes beforehand and instead of making a separate addon

Stop, stop! I can only become so erect. This would be awesome

[ZOS_ChipHilseberg]

I went ahead and added an {APIVersion} variable that is substituted with the current version in any paths listed in the addon ToC. I'll try to make a case for this for the next update (2.1).

[sirinsidiator]

Thank you very much! That will come in really handy in the future.
Will this go into one of the next incremental patches, or what else will the variable resolve to in the current live version in case it only makes it into update 2.1?

And just out of curiosity, are there any other substitutions besides ${language}?