Expand description
HTTP handlers
Generated by metaphor-schema. Do not edit manually.
These handlers use Axum and backbone-core’s BackboneCrudHandler to provide all 12 standard Backbone CRUD endpoints.
Re-exports§
pub use pos_closing_entry_handler::create_pos_closing_entry_routes;pub use pos_closing_entry_handler::create_pos_closing_entry_read_routes;pub use pos_closing_entry_handler::create_pos_closing_entry_write_routes;pub use pos_invoice_handler::create_pos_invoice_routes;pub use pos_invoice_handler::create_pos_invoice_read_routes;pub use pos_invoice_handler::create_pos_invoice_write_routes;pub use pos_invoice_item_handler::create_pos_invoice_item_routes;pub use pos_invoice_item_handler::create_pos_invoice_item_read_routes;pub use pos_invoice_item_handler::create_pos_invoice_item_write_routes;pub use pos_payment_handler::create_pos_payment_routes;pub use pos_payment_handler::create_pos_payment_read_routes;pub use pos_payment_handler::create_pos_payment_write_routes;pub use pos_profile_handler::create_pos_profile_routes;pub use pos_profile_handler::create_pos_profile_read_routes;pub use pos_profile_handler::create_pos_profile_write_routes;pub use pos_opening_entry_handler::create_pos_opening_entry_routes;pub use pos_opening_entry_handler::create_pos_opening_entry_read_routes;pub use pos_opening_entry_handler::create_pos_opening_entry_write_routes;pub use pos_cash_movement_handler::create_pos_cash_movement_routes;pub use pos_cash_movement_handler::create_pos_cash_movement_read_routes;pub use pos_cash_movement_handler::create_pos_cash_movement_write_routes;pub use pos_discount_handler::create_pos_discount_routes;pub use pos_discount_handler::create_pos_discount_read_routes;pub use pos_discount_handler::create_pos_discount_write_routes;pub use pos_manager_pin_handler::create_pos_manager_pin_routes;pub use pos_manager_pin_handler::create_pos_manager_pin_read_routes;pub use pos_manager_pin_handler::create_pos_manager_pin_write_routes;pub use pos_floor_plan_handler::create_pos_floor_plan_routes;pub use pos_floor_plan_handler::create_pos_floor_plan_read_routes;pub use pos_floor_plan_handler::create_pos_floor_plan_write_routes;pub use pos_table_handler::create_pos_table_routes;pub use pos_table_handler::create_pos_table_read_routes;pub use pos_table_handler::create_pos_table_write_routes;pub use guarded_routes::create_guarded_pos_priced_route;pub use guarded_routes::create_guarded_pos_priced_route_with_outbox;pub use guarded_routes::create_guarded_pos_routes;pub use guarded_routes::create_guarded_pos_routes_with_outbox;
Modules§
- guarded_
routes - Guarded route composition — the RECOMMENDED way to mount the POS module.
- pos_
cash_ movement_ handler - PosCashMovement REST handlers
- pos_
closing_ entry_ handler - PosClosingEntry REST handlers
- pos_
discount_ handler - PosDiscount REST handlers
- pos_
floor_ plan_ handler - PosFloorPlan REST handlers
- pos_
invoice_ handler - PosInvoice REST handlers
- pos_
invoice_ item_ handler - PosInvoiceItem REST handlers
- pos_
manager_ pin_ handler - PosManagerPin REST handlers
- pos_
opening_ entry_ handler - PosOpeningEntry REST handlers
- pos_
payment_ handler - PosPayment REST handlers
- pos_
profile_ handler - PosProfile REST handlers
- pos_
table_ handler - PosTable REST handlers
Structs§
- Company
Claims - The access-token claims a guarded surface trusts.
- Company
Context - The company + subject proven by a validated access token.
- Company
Verifier - Verifier the composing service builds once (from its JWT secret) and clones into guarded routes.
- Tenant
Claims - The access-token claims a guarded surface trusts.
- Tenant
Context - The company + subject proven by a validated access token.
- Tenant
Verifier - Verifier the composing service builds once (from its JWT secret) and clones into guarded routes.
Functions§
- company_
auth - Middleware: validate the Bearer token and insert a
CompanyContext; reject with 401 otherwise. - tenant_
auth - Middleware: validate the Bearer token and insert a
CompanyContext; reject with 401 otherwise.