How “solid” and “complete” are components in Bricks 2.0? Are they still considered “experimental”?
What if any “ToDo” list remains for components in Bricks?
The components have already left the experimental stage in 2.0 alpha (see changelog). Of course there are still current and future todos to extend the functionality.
In principle, however, there is no reason not to use them in development from now on, and productively from 2.0 stable onwards.
1 Like
You’ll run into issues very quickly, if you don’t check out and read the forum thoroughly to check what’s actually working and what not.
Restrictions apply very fast with loops, pagination and dynamic data.
Hmmmm… Two points of view here 
Maybe Bricks 2.0 release will address some of the concerns.
Using it in production and using it without pain are different kind of things. 
I didn’t say they are not working. They just don’t work as expected and don’t give you that much freedom.
@jmcbade I tested the latest RC, there won’t be major improvements till then anymore.
It’s best to form your own opinion. If you encounter any issues, please let us know, and we will, as usual, take care of it.
You are welcome to share your needs and issues with us in detail @Maexxx 
Hi @timmse,
I had a question about the component…
Why do we need to create two properties for a component to control the query loop? One for the query loop (toggle) and one for the query settings. To be honest, I haven’t worked with components much. But this is the first thing I encountered in it and it was a little confusing to me.
You don’t need to. If you know that the loop is always active (which is usually the case), enable it in the main component. Then you only need one loop property to determine what the instance should loop through.
However, if you want to enable or disable the loop for whatever reason in any instance, you need a toggle property to do so, since it’s a different control.
1 Like
Look at all my most recent posts, they list everything I noticed, even things outside components that lead to restrictions for the components as they are now.
They include closed bugs, which are now feature requests
We need this query loop element (SNN-BRX Child Theme, advanced features and gsap animations, acf, smtp, security, 301 logs, 404 logs, search logs - #91 by sinanisler) in Bricks natively to solve follow up inconveniences. Hence, it would be possible to create one blog post card component with properties for title, image, date and optional meta info etc. and use it with any query loop and also for static content. The component is no longer tightly coupled with its query loop. It can be used for a ‘posts’ query or a CPT ‘events’ and even a static card.
When all related elements like pagination and Query Results Summary work with such a setup, then the components implementation is solid and useful IMO.
It is missing basic functionality, decicde yourself.
Passing a property to a sub-component: NOT SUPPORTED.
Using a card component in a loop, and with static content: NOT SUPPORTED
Using a card component in ‘posts’ and ‘events’ loop: NOT SUPPORTED