Checking checkboxes updates in the backend but not the frontend
Hi ! I built a checklist . I noticed that while the back -end updates correctly , the visual representation in the checkbox doesn 't always reflect these changes . I 'm trying to figure out why the checkbox in a row remains checked even when the item it belongs to moves down due to the item sorting . If anyone has insights on this issue & sees what I am overlooking , please let me know ! I have added a video to show what I mean : https://www.loom.com/share/3930db8c89094bb383bd285584e2c583?sid=98a4fdd8-5d33-4e1c-ae66-28358d4117d8 The overall setup is complex as it is an expandable list with expandable items , but I had the same issue before I added the expansion . Also please ignore /forgive the complexity of my app atm - the next item on my list is to change the parts that should be components to components - it is intimidating to take that step though . . . It doesn 't determine it 's current value rather than an input I mean There are a few ways you can go about it An example is a 'toggle ' element . They 're really checkboxes under the hood but styled as a toggle so you mean to build a component that functions as a checkbox (eg when it is clicked it takes a different color and sets a variable ) ? It doesn 't need to hold a variable itself if you don 't want it to , it can just rely directly on the input value (for example via attributes ) But the main point is that the visual 'checked ' state would come from the data That might be a place to easily grab it from I built the component - and then had the exact same behavior π luckily it was a quick fix and I just had to exchange basing the visual state on the attribute instead of a variable . In the meantime , I also created components for my repeating titles and menu -bar . This is great and really not that hard , I should have started earlier π Thank you @Lucas G ! π₯2
