-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Adopt runtime settings from runtimeconfig.json in Blazor #35010
Comments
Supporting this will require option workloads so we'll need to emit a warning in the case that the workload is not installed. |
I'm not sure how this will work, we don't flow runtimeconfig.json to the browser as far as I'm aware |
This issue was created based on Larry's comment in my PR for supporting runtimeconfig.json file for WASM. (dotnet/runtime#56486 (comment)) TBH, I have very minimal knowledge about how Blazor works. I also don't know if this is a valid use case for Blazor customers. If it is, we probably should figure out how to make it work and I am happy to help in whichever way possible. If it isn't, feel free to close this issue. |
@lewing could you elaborate on what this is required for? Is this essential for 6.0 and are there scenarios that are blocked in the absence of this? |
Ping @lewing |
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Hi. Thanks for contacting us. |
I am working on adding the code to support parsing
runtimeconfig.json
for webassembly apps. (dotnet/runtime#38433 should be merged soon) Something similar needs to be done here, so that Blazor apps could honor the runtime settings fromruntimeconfig.json
file.The text was updated successfully, but these errors were encountered: