re_component_fallbacks 0.31.3

Handles registering various component fallbacks to `FallbackProviderRegistry`.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

//! This crate implements various component fallbacks.
//!
//! The only entry point is [`create_component_fallback_registry`], which registers all component type, and
//! component identifier fallbacks to a new [`FallbackProviderRegistry`].
//! This should be called by `re_viewer` on startup.
//!
//! ## Recommendation for where to put fallbacks
//!
//! Component fallbacks should be registered here **if**:
//! - They're not the same as the `provided_fallback` from
//!   reflection, i.e the default implementation is already what you want.
//! - And they're used in more than one view.
//! - And doesn't require specific dependencies from views that makes it not possible to add here without
//!   adding dependencies.
//!
//! Otherwise the fallback should be registered in the view class it's used in, on that view classes' `on_register` method.

use re_viewer_context::FallbackProviderRegistry;

mod blueprint_component_fallbacks;
mod component_fallbacks;

/// Creates a new [`FallbackProviderRegistry`] and registers built-in
/// type and archetype field fallbacks.
pub fn create_component_fallback_registry() -> FallbackProviderRegistry {
    let mut registry = FallbackProviderRegistry::default();

    blueprint_component_fallbacks::type_fallbacks(&mut registry);
    blueprint_component_fallbacks::archetype_field_fallbacks(&mut registry);

    component_fallbacks::type_fallbacks(&mut registry);
    component_fallbacks::archetype_field_fallbacks(&mut registry);

    registry
}