Fix issue with new elements in stream DOM test #2677
Merged
+17
−1
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.
I encountered this issue testing pagination with stream resets. Going to next page the first time worked, but subsequent stream resets failed (though it worked just fine in the browser).
This is due to the container id check. New items don't have any parent because the id would be unique. It just skips the element entirely, thus not setting the
data-phx-stream
value. It works the first time because the DOM already has the first list with ids.The simplest fix I could think of was just to ignore if parent_id is nil (this means new unique item), but not sure I like this because what happens if you have multiple lists? Wouldn't it just update all lists? I couldn't grok how this is dealt with in JS, so I'm leaving it for now.