Stone.js API
    Preparing search index...

    Interface RouteMapperOptions<IncomingEventType, OutgoingResponseType>

    Configuration options for the RouteMapper.

    interface RouteMapperOptions<
        IncomingEventType extends IIncomingEvent = IIncomingEvent,
        OutgoingResponseType = unknown,
    > {
        bindings?: Record<string, IBoundModel | BindingResolver>;
        composableProps?: string[];
        defaults?: Record<string, unknown>;
        dependencyResolver?: DependencyResolver;
        dispatchers: IDispatchers<IncomingEventType, OutgoingResponseType>;
        matchers: IMatcher<IncomingEventType, OutgoingResponseType>[];
        maxDepth: number;
        prefix?: string;
        protocolPolicy?: ProtocolPolicy;
        rules?: Record<string, RegExp>;
        strict?: boolean;
    }

    Type Parameters

    Index
    bindings?: Record<string, IBoundModel | BindingResolver>
    composableProps?: string[]

    Module props that compose down a group instead of being replaced by the child's value.

    The router carries module props without knowing them, and the default merge is child-wins, which is right for most: a child's contract is its contract. Some props are gates, and a gate declared on a group must hold for every child on top of the child's own: authz above all. A module declares its own key composable through its blueprint (stone.router.composableProps), so the router still names no module. Parent first, for the same reason group middleware runs first: a group encloses its routes.

    defaults?: Record<string, unknown>
    dependencyResolver?: DependencyResolver
    maxDepth: number
    prefix?: string
    protocolPolicy?: ProtocolPolicy
    rules?: Record<string, RegExp>
    strict?: boolean