-
Notifications
You must be signed in to change notification settings - Fork 10.4k
#51611 - Extended Blazor server and webassembly options to match web format. #54649
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
Conversation
@dotnet-policy-service agree |
Update .NET SDK to version 9.0.100-preview.5.24253.17. --- updated-dependencies: - dependency-name: Microsoft.NET.Sdk dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…00-preview.5.24253.17 Update .NET SDK to 9.0.100-preview.5.24253.17
Update .NET SDK to version 9.0.100-preview.6.24309.2. --- updated-dependencies: - dependency-name: Microsoft.NET.Sdk dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…100-preview.6.24309.2 Update .NET SDK to 9.0.100-preview.6.24309.2
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to revoke the approval, but we'll likely need tests to ensure that this doesn't break in the future. E2E tests are probably the easiest way to test this (rather than trying to test the Boot.*.ts
code directly).
Related to #56758. We'd only want to take one of these changes, as they do the same thing. |
Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime. |
@khamzakhamzakhamza Thank you for your contribution and sorry for a late reply. We need some automated tests validating that options are correctly propagated. The easiest way to achieve it is through E2E test. There are tests that contains some startup options and we need to modify them to run once with wasm/server options as they do now and second with options matching web format. For WebAssembly such test candidate might be https://github.com/dotnet/aspnetcore/blob/main/src/Components/test/E2ETest/Tests/WebAssemblyConfigureRuntimeTest.cs#L33 that is running https://github.com/dotnet/aspnetcore/blob/main/src/Components/test/testassets/BasicTestApp/wwwroot/index.html#L66-L70. For Server we probably need to create a new test |
@maraf ... It looks like this won't make Preview 1. I have the docs PR ( |
Hi @khamzakhamzakhamza. |
@maraf @javiercn ... DAH! 😄 ... I have the docs PR ( |
@lewing ... This closed again. Let me know if it's going to be dropped ... I'll close the docs PR if that happens. |
#51611 - Extended Blazor server and webassembly options to match web format.
Extends options consumed by the
Blazor.start()
method inblazor.server.js
andblazor.webassembly.js
to match how they work inblazor.web.js
and in the documentation.Description
I followed the design proposed by @MackinnonBuck and implemented the suggested changes. I have tested changes locally and everything works as expected.
I couldn't find any unit or integration tests for the Boot classes and felt hesitant to create new ones. However, I am happy to do so if someone from the team decides they are needed.