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.

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

[Blazor] Ensure WebAssembly startup options are initialized just once #59905

Merged
merged 5 commits into from
Jan 22, 2025

Conversation

maraf
Copy link
Member

@maraf maraf commented Jan 16, 2025

  • Ensure WebAssembly startup options are initialized just once, in case they are not passed by the user.
  • Remove .gitignore from Components.TestServer

Fixes #54049

@maraf maraf added the area-blazor Includes: Blazor, Razor Components label Jan 16, 2025
@maraf maraf self-assigned this Jan 16, 2025
@maraf maraf changed the title [Blazor] Ensure WebAssembly options [Blazor] Ensure WebAssembly startup options are initialized just once Jan 21, 2025
@maraf maraf marked this pull request as ready for review January 21, 2025 13:30
@maraf maraf requested a review from a team as a code owner January 21, 2025 13:30
@lewing
Copy link
Member

lewing commented Jan 22, 2025

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@maraf maraf merged commit e42a2b0 into dotnet:main Jan 22, 2025
27 checks passed
@maraf maraf deleted the BlazorEnsureWasmOptions branch January 22, 2025 07:42
@dotnet-policy-service dotnet-policy-service bot added this to the 10.0-preview1 milestone Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Blazor] WebAssembly JS initializers don't execute unless webAssembly options are provided to Blazor.start()
3 participants