Skip to content

Evaluate fingerprinting test data in Blazor.BuildPublishTests.DefaultTemplate_CheckFingerprinting #112814

Closed

Description

@maraf

The BlazorWasmSDK was previously enforcing WasmFingerprintDotnetJs=false. That changed in dotnet/sdk#46233 and now it is driven by WasmSDK and WriteImportMapToHtml property.

We should evaluate whether the Blazor.BuildPublishTests.DefaultTemplate_CheckFingerprinting is still meaningful

Activity

  1. added
    arch-wasmWebAssembly architecture
    os-browserBrowser variant of arch-wasm
    test-enhancementImprovements of test source code
    on Feb 22, 2025
  2. added this to the 10.0.0 milestone on Feb 22, 2025
  3. ghost added
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Feb 22, 2025
  4. dotnet-policy-service commented on Feb 22, 2025

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing
    See info in area-owners.md if you want to be subscribed.

  5. added
    in-prThere is an active PR which will close this issue when it is merged
    on Feb 24, 2025
  6. removed
    needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area owners
    on Mar 3, 2025
  7. locked and limited conversation to collaborators on May 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

arch-wasmWebAssembly architecturearea-VM-meta-monoin-prThere is an active PR which will close this issue when it is mergedos-browserBrowser variant of arch-wasmtest-enhancementImprovements of test source code

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions