Component Initial HTML #27
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I want to mention that this PR is currently nonfunctional due to Mostly opening this PR as a discussion as whether or not this concept can/should be pursued. There are several situations where it'd be useful to have a fallback that is not reliant on websockets. |
2 tasks
|
I think this can be addressed once reactive-python/reactpy#581 is completed. |
|
I'm going to close this in prioritization of SSR within IDOM v3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea of this PR is to allow for customizable initial HTML.
This is useful for...
This is different than an IDOM Core
idom.componentfallback=...that we have discussed due to the fact that this implementation fallback has no WS reliance.