If there's such a thing as too many filters, we haven't found it yet. But it doesn't hurt to turn off filters that we're not using, right? We could have "suppress_filters" set to true by default, which would prevent any filters from firing. To enable them, the atom would just need to include the argument "suppress_filters" => false.
This could go for both Organisms & Atoms-- however, there are probably some filters that should always fire. For instance, the args variable needs to be accessible so that we can set suppress_filters to false if we can't do it manually (ACF flex content layouts would fit this example).
If there's such a thing as too many filters, we haven't found it yet. But it doesn't hurt to turn off filters that we're not using, right? We could have "suppress_filters" set to true by default, which would prevent any filters from firing. To enable them, the atom would just need to include the argument
"suppress_filters" => false.This could go for both Organisms & Atoms-- however, there are probably some filters that should always fire. For instance, the args variable needs to be accessible so that we can set suppress_filters to false if we can't do it manually (ACF flex content layouts would fit this example).