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

Adopt runtime settings from runtimeconfig.json in Blazor #35010

Closed
fanyang-mono opened this issue Aug 3, 2021 · 7 comments
Closed

Adopt runtime settings from runtimeconfig.json in Blazor #35010

fanyang-mono opened this issue Aug 3, 2021 · 7 comments
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly

Comments

@fanyang-mono
Copy link
Member

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 from runtimeconfig.json file.

@fanyang-mono fanyang-mono added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Aug 3, 2021
@lewing
Copy link
Member

lewing commented Aug 4, 2021

Supporting this will require option workloads so we'll need to emit a warning in the case that the workload is not installed.

@javiercn
Copy link
Member

javiercn commented Aug 4, 2021

I'm not sure how this will work, we don't flow runtimeconfig.json to the browser as far as I'm aware

@fanyang-mono
Copy link
Member Author

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.

@pranavkm
Copy link
Contributor

pranavkm commented Aug 5, 2021

@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?

@mkArtakMSFT
Copy link
Member

Ping @lewing

@mkArtakMSFT mkArtakMSFT added investigate enhancement This issue represents an ask for new feature or an enhancement to an existing one and removed investigate labels Aug 10, 2021
@mkArtakMSFT mkArtakMSFT added this to the Backlog milestone Aug 10, 2021
@ghost
Copy link

ghost commented Aug 10, 2021

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.

@mkArtakMSFT mkArtakMSFT modified the milestones: Backlog, BlazorPlanning Nov 5, 2023
@mkArtakMSFT
Copy link
Member

Hi. Thanks for contacting us.
We're closing this issue as there was not much community interest in this ask for quite a while now.
You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.

@mkArtakMSFT mkArtakMSFT closed this as not planned Won't fix, can't repro, duplicate, stale Nov 19, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Feb 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly
Projects
None yet
Development

No branches or pull requests

5 participants