Fix duplicate cache invalidation token #308
Merged
Conversation
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
Collaborator
Cherry pick to beta success |
gmilano
previously approved these changes
Nov 19, 2020
The cache invalidation token was being added twice to deferred JavaScript files.
ncardeli
force-pushed
the
fix/duplicate-cache-invalidation-token
branch
from
b609cac to
02adc05
Compare
Collaborator
Cherry pick to beta success |
jechague
approved these changes
Nov 20, 2020
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.
The cache invalidation token was being added twice to deferred JavaScript files #260. This came up in DotNet after genexuslabs/DotNetClasses#260 and the same happened in Java.
Related PR in DotNet: genexuslabs/DotNetClasses#262
Changes proposed in this Pull Request
Issue:84288