Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Open
javiercn opened this issue Dec 13, 2024 · 0 comments
Open

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

javiercn opened this issue Dec 13, 2024 · 0 comments
Labels
area-blazor Includes: Blazor, Razor Components
Milestone
.NET 10 Planning

Comments

@javiercn
Copy link
Member

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
@dotnet-issue-labeler dotnet-issue-labeler bot added the area-blazor Includes: Blazor, Razor Components label Dec 13, 2024
@javiercn javiercn added this to the .NET 10 Planning milestone Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Milestone
.NET 10 Planning
Development

No branches or pull requests
1 participant
@javiercn