V10 #139
Merged
V10 #139
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 001cfae.
This reverts commit 65bdb4c.
…undry-Developers/v10 V10 Changes
…er/master v10 additional fix
No changes to the logic, just formatting.
Removed deprecated warnings. Fixed update() calls that should be updateSource(). Fix League-of-Foundry-Developers#108 Fix League-of-Foundry-Developers#112 League-of-Foundry-Developers#113
…ster Some improvements
Update the documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey folks! Thanks for working on this wonderful module! As a pointer to future foundry users on v10, I though it might help to update the
v10branch's manifest to the 2.4.0 release? It should reduce the incidence of folks having issues like #136This just updates the v10 branch to
c9abb8b8917d2a594749c311b12c4a4dc3183ecc, the sha released as 2.4.0. I also put a tiny commit on top to make the module.json reflect the 2.4.0 release instead of latest so folks can just grab the module.json from the v10 branch.