You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add inline comments to formatter.md and lifecycle diagram to hello_world.md
- formatter.md: add ABAP inline comments before each binding variant
explaining what it does (one-field vs two-field, showMeasure/showNumber,
preserveDecimals, currencyCode, style short/long, digit sequence),
plus resolved UI5 output for the OData type section
- hello_world.md: add ASCII flow diagram showing the roundtrip lifecycle
(browser→main()→browser loop) to visualize that main is called on
every user interaction
https://claude.ai/code/session_01AaA4EMw83KMzGP6kaDZPJU
Copy file name to clipboardExpand all lines: docs/get_started/hello_world.md
+16-2Lines changed: 16 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,13 +55,27 @@ ENDCLASS.
55
55
```
56
56
57
57
### Event Handler
58
-
The `main` method is called on every roundtrip — that is, on initialization and after every user interaction (button press, input submit, etc.). To control what happens when, use `CASE abap_true` to distinguish between lifecycle events:
58
+
The `main` method is called on every roundtrip — that is, on initialization and after every user interaction (button press, input submit, etc.):
59
+
60
+
```
61
+
┌─────────┐ ┌──────────┐ ┌─────────┐
62
+
│ Browser │──────>│ main() │──────>│ Browser │
63
+
│ (Start) │ HTTP │ init │ HTTP │ (View) │
64
+
└─────────┘ └──────────┘ └────┬─────┘
65
+
│ user clicks
66
+
┌─────────┐ ┌──────────┐ ┌────┴─────┐
67
+
│ Browser │<──────│ main() │<──────│ Browser │
68
+
│ (Update) │ HTTP │ event │ HTTP │ (Event) │
69
+
└─────────┘ └──────────┘ └──────────┘
70
+
```
71
+
72
+
To control what happens when, use `CASE abap_true` to distinguish between lifecycle events:
59
73
60
74
-`client->check_on_init( )` — first call when the app starts
61
75
-`client->check_on_event( )` — user triggered an event (e.g. button press)
62
76
-`client->check_on_navigated( )` — returned from another app via navigation
63
77
64
-
This pattern works because each`check_*` method returns `abap_true` only for its specific phase, making `CASE abap_true` act as a dispatcher:
78
+
Each`check_*` method returns `abap_true` only for its specific phase, making `CASE abap_true` act as a dispatcher:
0 commit comments