I’ve been working some with components and using the Query property in Bricks 2.0 Beta. The feature works very well, but I’ve noticed that if we could have access to link properties inside the actual query it would speed things up greatly to reuse the component without setting it up every time.
I have some pretty complex custom post type queries with additional meta and taxonomy queries that change slightly depending on the page, so to be able to link those to the properties and values from the component properties settings (or even be dynamic) would be amazing.
Maybe I didn’t explain well, but that’s what I’m using. The idea is a LOT of what I’m setting up in that Query loop element is repetitive. With access to a link properties to a few fields inside that query loop element it would be much faster. Then you could link those data fields without actually editing/recreating the majority of the query every time. Just input different post types, taxonomies, or meta values instead of rebuilding the whole query every time.
Or maybe I don’t know what I’m doing and you actually can do that already.
No, you can’t do that with Bricks and that’s one of the major reasons why components in Bricks are “not usable” as some would say.
You use the query loop tied to a component. I talk about a magic query loop element that has no code output itself and in which you can nest any element and it gets looped. The loops being tied to an element in Bricks now turn out to be a major drawback.
