de5486725d
# Objective Some usecases in the ecosystems are blocked by the inability to stop bevy internals and third party plugins from touching their entities. However the specifics of a general purpose entity disabling system are controversial and further complicated by hierarchies. We can partially unblock these usecases with an opt-in approach: default query filters. ## Solution - Introduce DefaultQueryFilters, these filters are automatically applied to queries that don't otherwise mention the filtered component. - End users and third party plugins can register default filters and are responsible for handling entities they have hidden this way. - Extra features can be left for after user feedback - The default value could later include official ways to hide entities --- ## Changelog - Add DefaultQueryFilters |
||
|---|---|---|
| .. | ||
| access.rs | ||
| builder.rs | ||
| error.rs | ||
| fetch.rs | ||
| filter.rs | ||
| iter.rs | ||
| mod.rs | ||
| par_iter.rs | ||
| state.rs | ||
| world_query.rs | ||