Add cache support for Flash/AIR SWF library processing#47
Open
barisyild wants to merge 1 commit intoopenfl:masterfrom
Open
Add cache support for Flash/AIR SWF library processing#47barisyild wants to merge 1 commit intoopenfl:masterfrom
barisyild wants to merge 1 commit intoopenfl:masterfrom
Conversation
The Flash/AIR branch in processLibraries was missing the cache mechanism
that the Animate branch already had. This caused generateSWFClasses to
re-parse the SWF from scratch on every build even when the source file
and tool had not changed.
The cache stores generated class names and template asset data in a JSON
file at {targetDirectory}/obj/libraries/{name}.cache, using the same
mtime-based invalidation strategy as the Animate branch.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The Flash/AIR branch in processLibraries was missing the cache mechanism that the Animate branch already had. This caused generateSWFClasses to re-parse the SWF from scratch on every build even when the source file and tool had not changed.
The cache stores generated class names and template asset data in a JSON file at {targetDirectory}/obj/libraries/{name}.cache, using the same mtime-based invalidation strategy as the Animate branch.