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.
Template files have a habit of sticking around in the output folder, even if the project no longer needs or wants them. But if we save a list of templates after a build, we can compare against that list in future builds to locate no-longer-used files.
The intent is for
deleteStaleTemplates()
to run every time. It doesn't just delete the files, it saves the list for next time. A drawback of this implementation is that if it gets skipped, the list doesn't get updated, and if the list isn't updated, the next run might not find all the stale templates. This can of course be fixed with a clean build.Like #27, this is one half of a potential solution to openfl/lime#1546. (The other half is openfl/lime#1550.) And I'd argue it's a better solution, requiring less maintenance and having no 31-character-long function names.