Skip to content

[Blazor] Get rid of special webassembly behavior in the static web assets SDK #59468

Open
@javiercn

Description

@javiercn

In particular, we allow defining assets with an ItemSpec that points to a location that doesn't exist, and we have logic all over the place to fallback on the original item spec. That is not only costly, but error prone.

Recently, a bug was discovered that was caused because we didn't account for this ItemSpec behavior.

We should define webassembly assets properly and get rid of this problematic behavior on the SDK

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority:1Work that is critical for the release, but we could probably ship withoutarea-blazorIncludes: Blazor, Razor Components

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions