Conditional static asset updating #2876
Merged
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
ghostwords
force-pushed
the
smarter-asset-updating
branch
from
74a1511 to
6f8230a
Compare
Instead of unconditionally on every extension startup.
ghostwords
force-pushed
the
smarter-asset-updating
branch
from
6f8230a to
c22cd4f
Compare
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.
This changes static asset update behavior on extension startup. Instead of happening on every startup, an asset update will take place only if enough time elapsed since last update.
The very first startup following extension installation is a special case where asset updates will happen just as they do now.
When the extension stays continuously active, asset update behavior should also remain the same as now.
Part of #2579.