Module prelude 

Common re-exports for convenient access to core functionality

This module provides a single import point for all commonly used Ri components, simplifying application code and reducing the number of import statements.

Usage

use ri::prelude::*;
 
#[tokio::main]
async fn main() -> RiResult<()> {
    let app = RiAppBuilder::new()
        .with_config("config.yaml")?
        .build()?;
     
    app.run(|ctx| async move {
        ctx.logger().info("service", "Ri service started")?;
        Ok(())
    }).await
}

Re-exports

pub use crate::core::RiAppBuilder;

pub use crate::core::RiAppRuntime;

pub use crate::core::RiServiceContext;

pub use crate::core::RiModule;

pub use crate::core::RiError;

pub use crate::core::RiResult;

pub use crate::core::RiLockError;

pub use crate::core::RiPythonModule;

pub use crate::core::RiPythonModuleAdapter;

pub use crate::core::RiPythonServiceModule;

pub use crate::core::RiPythonAsyncServiceModule;

pub use crate::core::RiErrorChain;

pub use crate::core::RiErrorChainIter;

pub use crate::core::RiErrorContext;

pub use crate::core::RiOptionErrorContext;

pub use crate::core::RiHealthStatus;

pub use crate::core::RiHealthCheckResult;

pub use crate::core::RiHealthCheckConfig;

pub use crate::core::RiHealthReport;

pub use crate::core::RiHealthChecker;

pub use crate::service_mesh::health_check::RiHealthCheckType;

pub use crate::service_mesh::health_check::RiHealthSummary;

pub use crate::core::RiLifecycleObserver;

pub use crate::core::RiLogAnalyticsModule;

pub use crate::fs::RiFileSystem;

pub use crate::log::RiLogger;

pub use crate::log::RiLogConfig;

pub use crate::log::RiLogLevel;

pub use crate::config::RiConfig;

pub use crate::config::RiConfigManager;

pub use crate::hooks::RiHookBus;

pub use crate::hooks::RiHookEvent;

pub use crate::hooks::RiHookKind;

pub use crate::hooks::RiModulePhase;

pub use crate::cache::RiCacheModule;

pub use crate::cache::RiCacheConfig;

pub use crate::queue::RiQueueModule;

pub use crate::queue::RiQueueConfig;

pub use crate::gateway::RiGateway;

pub use crate::gateway::RiGatewayConfig;

pub use crate::gateway::RiRoute;

pub use crate::gateway::RiRouter;

pub use crate::gateway::load_balancer::RiBackendServer;

pub use crate::gateway::load_balancer::RiLoadBalancerServerStats;

pub use crate::gateway::load_balancer::RiLoadBalancer;

pub use crate::gateway::load_balancer::RiLoadBalancerStrategy;

pub use crate::device::RiDeviceControlModule;

pub use crate::device::RiDeviceControlConfig;

pub use crate::device::RiDeviceSchedulingConfig;

pub use crate::device::RiDevice;

pub use crate::device::RiDeviceType;

pub use crate::auth::RiAuthModule;

pub use crate::auth::RiAuthConfig;

pub use crate::service_mesh::RiServiceMesh;

pub use crate::service_mesh::RiServiceMeshConfig;

pub use crate::service_mesh::RiServiceMeshStats;

pub use crate::service_mesh::RiServiceEndpoint;

pub use crate::service_mesh::RiServiceHealthStatus;

pub use crate::observability::RiObservabilityModule;

pub use crate::observability::RiObservabilityConfig;

pub use crate::observability::RiTracer;

pub use crate::observability::RiMetricsRegistry;

pub use crate::database::RiDatabaseConfig;

pub use crate::database::DatabaseType;

pub use crate::database::RiDatabasePool;

pub use crate::database::RiDBRow;

pub use crate::database::RiDBResult;

pub use crate::module_rpc::RiModuleRPC;

pub use crate::module_rpc::RiModuleClient;

pub use crate::module_rpc::RiModuleEndpoint;

pub use crate::module_rpc::RiMethodCall;

pub use crate::module_rpc::RiMethodResponse;