-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
Component not correctly rendered #2531
Comments
{
...
key: product.id,
quantity: product.cartQuantity,
id: 'product-card-'~product.id~product.cartQuantity,
} Just in case, did you check you have no duplicate id (due to the concatenation of
(same if you have a cartQuantity resolving to null or false) Anyway, I would not use |
Thanks for your fast reply, In my case this product.id is an UUID v4 and will never collate with another one. Perhaps it has something to do with performance and too much ProductCard loaded on the same ? |
Are we talking about LiveComponent ? Could you share you PHP component class ? |
With no way to reproduce, i fear it will be hard to investigate. Just sharing personal experience, most of the time this kind of glitches are due to malformed HTML... or anything blocking morphing to happen correctly. Could you try with (https://symfony.com/bundles/ux-live-component/current/index.html) |
Bug Report: Intermittent Product Card Component Rendering Failure
Description of the Problem
The ProductList component occasionally fails to properly render ProductCard components, resulting in empty divs with only IDs being output instead of the full product card content. This occurs within a nested loop structure that renders product cards for different categories and subcategories.
Expected Behavior
Actual Behavior
Code Example
Additional Information
Environment
Questions for Investigation
Additional Context
I'm currently unable to provide a minimal reproduction repository due to the intermittent nature of the issue. I'll continue attempting to create a reliable reproduction case and update the issue when available.
💡 If you need any additional information or clarification, please let me know. I'm happy to provide more details or investigate specific aspects of the problem.
The text was updated successfully, but these errors were encountered: