During my last PR I had gotten a little lost in the structure of the module... so I decided to try to do something about it.
One thing I always try to do when I can is to force the standard league template structure into the various module projects, for example use the same folder names "scripts" , styles" , etc. because that is the most commonly used structure and it helps the various developers find themselves in someone else's code.
In addition I added a github action to create releases in a more automated way (the varriount plugin is commented out by default because I don't know if they like to have it active by default), just click on the new release button and create a tag with the syntax vX.X.X and a release with the same name vX.X.X (Note: Make sure you have given write permissions to github actions on the project)
What I tried to impose is the standard used by other foundry modules like "Item Piles", "Chat Portrait", etc., I don't think there are any problems but let me know
During my last PR I had gotten a little lost in the structure of the module... so I decided to try to do something about it.
One thing I always try to do when I can is to force the standard league template structure into the various module projects, for example use the same folder names "scripts" , styles" , etc. because that is the most commonly used structure and it helps the various developers find themselves in someone else's code.
In addition I added a github action to create releases in a more automated way (the varriount plugin is commented out by default because I don't know if they like to have it active by default), just click on the new release button and create a tag with the syntax vX.X.X and a release with the same name vX.X.X (Note: Make sure you have given write permissions to github actions on the project)
What I tried to impose is the standard used by other foundry modules like "Item Piles", "Chat Portrait", etc., I don't think there are any problems but let me know