FlutterFlow Nested ListView of Information
Вставка
- Опубліковано 6 вер 2024
- In this video, we will cover how to have nested ListView in FlutterFlow so you can show information at different depths. This structure is used quite commonly across social platforms like Reddit, Hacker News and Product Hunt.
Please remember to Like, Comment or Subscribe for more videos on FlutterFlow!
-----
Need help? Book a chat here: cal.com/stevenliu
Want to support me? buy.stripe.com/28o2as3FY1in2QMaEF
This is awesome Steven! Exactly what I needed to understand a problem I was trying to solve.
I'm happy this helped you! :)
thanks man exactly what i was looking for. you solved my problem!! :)
Glad I could help!
Hello, what if I use a textfield where the user can manipulate the displayed data. how can i update the json value at its exact path? 😀
Brilliant ❤
Hey please how would you suggest I do a similar thing for contacts. Eg. I am trying to build a contact list like the one iphone where names that begin with "A" are under "A" and "B" under "B" and so on.....If you have a solution or a vidoe please help me with the link or any assistance as to how i can proceed please?
Nice video! But what if I want to use the items in list of an App State?
Possible but will require careful consideration. Either your App State contains some JSON format (which is not recommended) or you create a custom Data Type where the first data type is a list, and then another data type is a list of the first data type and so on...a nested mess.
Hello, What if i want to show the data in next page like in cricbuzz app if you know and pass the parametrs is that possible can u tell me?????????????
Thank you sooo much ❤
Is is possible with supabase and flutterflow??
Hey! yes it is possible (just tested) however it will be dependent on how you've structured your tables.
What I mocked up was create a table called posts, create another table called comments_level1 with a foreign key to id in table posts (to identify what level 1 comment relates to what post). Then a deeper level would be another table called comments_Level2 with a foreign key to id in comments_level1 (so you know what comment in level 1 is comment level 2 replying to)...and so on. This is very inefficient and will only go as deep as you have created your tables unfortunately.
An easier way may be to have a table called posts and have a field of type JSON called comments where you store all your nested comments...
@@StevenNoCode On the other hand many systems like UA-cam only have a limited amount of comment levels so it’s ok I guess. Thanks for your insight on this!