Bug report:
If you have component instance, you canât set a condition for it. So as soon as you have a component you canât set condition for each instance.
I have the feeling these components will not reach a usable state within a year from now. Bricks 2.0 seems to miss the chance to do a major cleanup and remove the flaws and restrictions in the background.
Hi guys,
We added some of your improvements in Bricks 2.0 RC, which is now available in your account.
Best to check the changelog: Bricks 2.0-rc Changelog â Bricks
Please let us know if you are still experiencing issues or have suggestions for improvement.
As with any pre-stable release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.
its great
I think we have most of the basic property types for now
one thing left is allowing people to connect properties to anything
I mean all style tab inputs/controls should work with properties
probably too big decision before release so I guess it will happen in time all good. 
we have enough new tools features for the bricks 2.0 its amazing work congrats to team.
I agree, we should be able to set condition on the component instance, i couldnt find a way to do that even in the latest rc. Only way is to unlink the component and set the condition
Then it is not a component instance anymore. That doesnât make sense.
I donât understand in general, why Bricks component instances behave so much different and have so many specialities, when they should mostly behave like an any other element.
Just the backend should build the output based on the instructions from a unique place.
Open the component instance, then you can set the conditions - per instance.
Matej
The moment i added the condition in the component, it will be applied to all instances. Am i missing something?
he said instance component
edit:
@Matej they are saying instances doesnt show the condition icon at all
we should create new topic for this if this is a bug. lets wait Matej.
but I think its just not implemented. because which edge cases you would need it.
we will create components so we dont have to create similar or same design parts so we can use one component again and again.
if I am going to setup conditions for each instance whats the point? 
anyway maybe I am missing some edge cases thats my thinking for now.
A use case for instance, you have a section component that you would only like to show a particular instance if a certain condition is met e.g if the url contains a certain parameter.
not gonna lie after posting I think that too but we cant make section component slotable yet 
yep +1
HI @emmanuelson, you should be able to connect a property to the condition, then you can show / hide single instance it based on a property. But yes, if you just add a condition there, without property, it will affect all component instances.
If you just need to toggle it on/off, you can connect âtoggleâ property to the âHide elementâ part, and you should be able to toggle it.
That would solve the issue you have, right?
Matej
Why canât we just set a condition on the instance? Thatâs my feature request. Itâs far from a streamlined experience and steepens the learning curve, when having so many additional steps. Element level condition are well known now.
Hi @Maexxx,
yeah, the current implementation does not support adding conditions directly to the component instance, only via properties.
Letâs see how many users will request this.
Matej
That doesnât even work in v2.0 RC to hide a component at instance level, only sub-parts of a component.
The context menu does not allow you to hide the root element in the component editor. Thus, you canât link a toggle property to the root element and hide it on instance level. So the proposed solution does not work here.
@Maexxx, you should still be able to do it via âeyeâ icon, right?
Right, that is the only way that works. While the context menu would suggest that itâs not supported at all.
So, the context menu is missing the entry.
just realised what he wants is possible with my snn-brx conditions element because the conditions are exposed controls to the components properties.
emergent behaviour. more properties/controls supported better the system.
Yes, that will work too and I like the condition element.
Ever thought about creating a similar magic Query loop element, which also supports nesting of multiple elements?
