Fix 8 code snippet bugs across documentation

- logging.md: fix variable name factory(log) → factory(lo_log) (won't compile)
- popups.md: fix popover by_id='my_id' → by_id='TEST' (wrong anchor element)
- navigation.md: wrap _event_client() in follow_up_action() (result was unused)
- trouble.md: add missing DATA declaration for variable 'input'
- trouble.md: remove debugger; statement from JS snippet
- general.md: fix client->get( )->event → client->get( )-event (structure access)
- srtti.md: remove unused variable o_table
- dx.md: rename duplicate report zre_app_alv → zre_app_popup

https://claude.ai/code/session_01AaA4EMw83KMzGP6kaDZPJU

Author: claude

docs/development/general.md

@@ -62,7 +62,7 @@ CLASS z2ui5_cl_demo_app_001 IMPLEMENTATION.
 
     DATA(lt_arg) = client->get_event_arg( ).
 
-    CASE client->get( )->event.
+    CASE client->get( )-event.
       WHEN `BUTTON_POST`.
         client->message_toast_display( |{ mv_value } - send to the server| ).
     ENDCASE.

docs/development/navigation/navigation.md

@@ -52,11 +52,11 @@ Sound familiar? The abap2UI5 framework emulates the classic `call screen` and `l
 #### Launchpad
 We recommend using backend communication exclusively for view changes or popup calls. If you're using a launchpad, consider navigating through the launchpad to utilize browser navigation and history. Here's an example:
 ```abap
-client->_event_client(
-    val = client->cs_event-cross_app_nav_to_ext
-        t_arg  = VALUE #( ( 
-            `{ semanticObject: "Z2UI5_CL_LP_SAMPLE_04",  action: "display" }` 
-    ) ) ).
+client->follow_up_action( client->_event_client(
+    val   = client->cs_event-cross_app_nav_to_ext
+    t_arg = VALUE #( (
+        `{ semanticObject: "Z2UI5_CL_LP_SAMPLE_04",  action: "display" }`
+    ) ) ) ).
 ```
 To learn more about launchpads and routing, refer to the documentation [here.](/configuration/launchpad)
 

docs/development/popups.md

@@ -113,7 +113,7 @@ To display a popover, use the method `client->popover_display` and specify the I
                     press = client->_event( `POPOVER_CLOSE` ) ).
         client->popover_display(
             xml   = popover->stringify( )
-            by_id = `my_id` ).
+            by_id = `TEST` ).
 
       WHEN `POPOVER_CLOSE`.
         client->popover_destroy( ).

docs/development/specific/logging.md

@@ -54,7 +54,7 @@ METHOD z2ui5_if_app~main.
   lo_log->e( `This is an error...` ).
   lo_log->s( `This is a success message...` ).
 
-  client->nav_app_call( z2ui5_cl_pop_messages=>factory( log ) ).
+  client->nav_app_call( z2ui5_cl_pop_messages=>factory( lo_log ) ).
 
 ENDMETHOD.
 ```

docs/development/trouble.md

@@ -8,12 +8,13 @@ For UI5 input fields, the soft keyboard is automatically shown when focusing an
 
 METHOD z2ui5_if_app~main.
 
+    DATA input TYPE string.
+
     IF client->check_on_init( ).
-    
+
     DATA(view) = z2ui5_cl_xml_view=>factory( ).
     view->_generic( name = `script`
                     ns   = `html` )->_cc_plain_xml( `z2ui5.afterBE = (id , mode) => { ` &&
-                       `debugger;` &&
                         `var input = z2ui5.oView.byId(id).getDomRef();` &&
                         `input = input.childNodes[0].childNodes[0];` &&
                         `input.setAttribute("inputmode" , mode);` &&

docs/technical/dx.md

@@ -150,7 +150,7 @@ From here, it's just a small step to generate everything dynamically with RTTI 
 Anyone who has browsed SE37 for POPUP_TO_* knows the charm of classic ABAP popups. Function modules like `POPUP_TO_CONFIRM` are simple yet powerful:
 
 ```abap
-REPORT zre_app_alv.
+REPORT zre_app_popup.
 
 DATA event TYPE string.
 CALL FUNCTION `POPUP_TO_CONFIRM`

docs/technical/tools/srtti.md

@@ -69,7 +69,6 @@ CLASS z2ui5_cl_app IMPLEMENTATION.
       p_table_kind = cl_abap_tabledescr=>tablekind_std 
       p_unique     = abap_false ).
 
-    DATA: o_table TYPE REF TO data.
     CREATE DATA mr_tab TYPE HANDLE o_table_desc.
 
     client->message_box_display( `this works only with S-RTTI` ).