[LiveComponent] Adding more detail about loops & keys behavior #813
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
|
Docs look good! (Fyi, you have a commit from #811) |
kbond
reviewed
Apr 20, 2023
norkunas
reviewed
Apr 20, 2023
weaverryan
force-pushed
the
live-updating-loop-docs
branch
from
258fbe0 to
4fb2247
Compare
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.
One of the trickier things in any frontend system like this is dealing with loops of elements or components. This expands on the existing docs to clarify that
data-live-idis sometimes needed for loops of elements and also to explain an expected situation that might cause a WTF moment for people.Cheers!