From 7bac065b748237d7f1f0067048f43b270bec2c61 Mon Sep 17 00:00:00 2001 From: bbrtj Date: Mon, 8 Jul 2024 18:16:36 +0200 Subject: [PATCH] Add a note about KelpX::Controller --- lib/Kelp/Manual/Controllers.pod | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/lib/Kelp/Manual/Controllers.pod b/lib/Kelp/Manual/Controllers.pod index 091add1..10502a3 100644 --- a/lib/Kelp/Manual/Controllers.pod +++ b/lib/Kelp/Manual/Controllers.pod @@ -120,7 +120,11 @@ You no longer have to prefix destinations with the base controller class name. While reblessing is how core Kelp deals with controllers, it is entirely possible to introduce your own base controller classes. Most of the details remain the same, like setting C and C configuration, but your -main controller class does not have to inherit from your app class: +main controller class does not have to inherit from your app class. + +Below is a guide on how to implement that from scratch. Alternatively, +L module may be used, which comes with pre-implemented +custom base controller and context classes. =head3 Step 1: Custom Context object