using one style approach for all 3 configs WebAssembly, Web and Server

[vladimir-shirmanov]

[Blazor] Accept the blazor.web.js startup options format in blazor.{server|webassembly}.js

Description

Added config properties to blazor.{server|webassembly}.js to follow the same structure as blazor.web.js

Fixes #51611

[mkArtakMSFT]

@javiercn can you please review this? Thanks!

[azure-pipelines]

Commenter does not have sufficient privileges for PR 56758 in repo dotnet/aspnetcore

[vladimir-shirmanov]

reopening

/azp run

[vladimir-shirmanov]

Hi there, @javiercn @mkArtakMSFT, I don't have sufficient permissions to rerun the ci. What are the next steps for this PR?

[javiercn]

@vladimir-shirmanov we need some E2E tests (either new ones, or modify existing ones) to make sure that things are working and we don't break this in the future.

[vladimir-shirmanov]

@vladimir-shirmanov we need some E2E tests (either new ones, or modify existing ones) to make sure that things are working and we don't break this in the future.

Ok, let me think how to do that. Thanks

[MackinnonBuck]

Related to #54649. We'd only want to take one of these changes, as they do the same thing.

[javiercn]

We would need E2E tests to validate the behavior and make sure that it doesn't break in the future.

[Copilot]

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

src/Components/Web.JS/src/Platform/WebAssemblyStartOptions.ts:41

• [nitpick] The property name 'webAssembly' might be redundant since it has the same type as the interface itself. Consider renaming it to avoid redundancy.

webAssembly?: WebAssemblyStartOptions

[dotnet-policy-service]

Hi @vladimir-shirmanov.
It seems you haven't touched this PR for the last two weeks. To avoid accumulating old PRs, we're marking it as stale. As a result, it will be closed if no further activity occurs within 4 days of this comment. You can learn more about our Issue Management Policies here.