-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Allow to fingerprint Blazor.js #46988
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
e29ba35
Allow to fingerprint Blazor.js
maraf 6899891
Merge remote-tracking branch 'upstream/main' into BlazorJsFingerprint
maraf 5bf13db
Fix relative path for publish fingerprinted asset
maraf fa1f556
Update test to assert fingerprinted blazor.js
maraf c481361
Fix testasset used by other tests
maraf ca8be03
Merge branch 'main' into BlazorJsFingerprint
maraf 2d73722
Merge remote-tracking branch 'upstream/main' into BlazorJsFingerprint
maraf c1f17ed
Merge remote-tracking branch 'upstream/main' into BlazorJsFingerprint
maraf 4dcb1b7
Use BlazorFingerprintBlazorJs to switch FingerprintCandidates instead…
maraf File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part is confusing me a bit, do we rewrite blazor.js in any way during this whole process? If not, I'm not sure why this is needed at all.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's the same issue we have with runtime assets. If we do hard fingerprint during build, the asset to promote for publish has identity without fingerprint (
bin/Debug/wwwroot/_framework/blazor.js
), but the file on disk has fingerprint (bin/Debug/wwwroot/_framework/blazor.abcd.js
) and thus it complains that the file doesn't exist.This is fixing it by creating an asset that has fingerprint in identity.
Maybe we can do soft fingerprint during build and hard only during publish. Any ideas?