Nice one Pooja. In had an understanding from looking at the generated code but it's super clear having you explain. There are so many weird scenarios I use conditional builder to limit my backend calls.
can i ask, why the simple search do not use the conditional builder according for flutterflow document, When we don't use the conditional builder, use the conditional visibility, the two list view will count query two time from firebase?
Love this Pooja!! You are the best! Would love to know how to handle responsiveness -- Should we use responsive visibility or conditional builder and then responsive breakpoints being the condition? I am mainly wondering from a best practice / performance perspective.
Thank you Andrew 💜 And responsive visibility may be better because it handles most of the cases and under the hood, its still "if else" so it renders one child at a time + handles the breakpoints in a more cleaner way. But I can dig into this topic more and see if I can create a video about best practices around responsiveness once I find more details. Thank you again :)
I needed a more detailed example and how you did it in practice, I myself can't recreate this counter system and how you did it to show or not the responses to the comments, I made my comment counter using supabase query and filtering the post id with the comment id and putting it in a text as the number of items, I have no idea how to hide it from the interface when there are no comments.
If they are dependent on the same variable (like one should be rendered on true, and one on false), only one of them will render at any time (bcz they are inside a Column, so in generated code its doing a if() block)
@@FlutterFlow thank you for your reply but still I am confused that what is the use of conditional builder because listview Or rows are always inside a parent column while building a widget tree
@@chinmaykhandelwal7171 Check out the last part of the video where we summarize the usecases. Like if you are creating a component, the root widget doesnt necessarily have to be a column. (You only care about the direct parent) Also major usecase for a conditional builder is when you have multiple UI elements for 1+ or 2+ conditions, so "if, else if, else if, else"
Do you always have an else condition 99% of the cases? Because conditional builder requires a widget for the else condition everytime and sometimes we just want to hide/show things and not switch UI (and using an empty container for "else" may not be a good practice)
