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.

Sign up for GitHub

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

Jump to bottom

We can interleave Static/Server/WebAssembly components within an app #46394

Closed
mkArtakMSFT opened this issue Feb 1, 2023 · 2 comments
Closed

We can interleave Static/Server/WebAssembly components within an app #46394

mkArtakMSFT opened this issue Feb 1, 2023 · 2 comments
Assignees
@MackinnonBuck
Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-full-stack-web-ui Full stack web UI with Blazor Priority:1 Work that is critical for the release, but we could probably ship without
Milestone
8.0-preview6

Comments

@mkArtakMSFT
Copy link
Member

mkArtakMSFT commented Feb 1, 2023 •
edited by javiercn
Loading

@MackinnonBuck I'll let you take the lead on filling the details here, since you've been prototyping this.
@mkArtakMSFT mkArtakMSFT added 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 Priority:1 Work that is critical for the release, but we could probably ship without feature-full-stack-web-ui Full stack web UI with Blazor labels Feb 1, 2023
@mkArtakMSFT mkArtakMSFT added this to the .NET 8 Planning milestone Feb 1, 2023
@mkArtakMSFT mkArtakMSFT added area-blazor Includes: Blazor, Razor Components and removed feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Feb 1, 2023
@mkArtakMSFT mkArtakMSFT mentioned this issue Feb 1, 2023
Closed
@danroth27 danroth27 mentioned this issue Feb 14, 2023
Closed
@mkArtakMSFT
Copy link
Member Author

Closing as this work is tracked by other issues already.

@mkArtakMSFT mkArtakMSFT closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2023
@Xyncgas
Copy link

Xyncgas commented May 27, 2023

Quick question, what's wrong with just having instances of renderer (conceptually), as components

So if I have a component that's server rendered, a component that's rendered in browser in webassembly, they are basically just communicating with the eventual presenter that generates the DOM from different locations what they are going to present next and let the presenter / observer to do the collection from these renderers and do diffing using the current mechanism

So simple, I've already done it couple months ago, is this what you plan to do

@ghost ghost locked as resolved and limited conversation to collaborators Jun 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@MackinnonBuck MackinnonBuck

Labels
area-blazor Includes: Blazor, Razor Components enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-full-stack-web-ui Full stack web UI with Blazor Priority:1 Work that is critical for the release, but we could probably ship without
Projects
None yet
Milestone
8.0-preview6
Development

No branches or pull requests
3 participants
@MackinnonBuck @mkArtakMSFT @Xyncgas