Clarify JSON handling approach in deprecations docs - #319
Merged
Merged
Conversation
…ader The utility-classes warning pointed at `z2ui5_cl_ui5_json` as the reader an app should use. That class was removed from abap2UI5 `src/02` on 2026-09-14 without ever having shipped in a release, so the sentence named an object no reader can find. What replaces it is what the apps already do: compose JSON as a string in ABAP and bind it with `_bind( val = ... json = abap_true )` outbound, read the one field you need with `find` / `substring_before` inbound. The payloads that reach an app are written by the framework and are flat, so that is the whole job - there is deliberately no released parser, and the page now says so rather than pointing somewhere. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019rmo8XKoBEpBRZ2TZMUQrF
This was referenced Sep 14, 2026
oblomov-dev
added a commit
that referenced
this pull request
Sep 14, 2026
…efacts (#321) abap2UI5/samples#843 promoted fourteen samples out of src/00/97 into src/01, and the links published here point at that repository's main - check.yml pins the checkout to it on purpose - so every one of those paths moved when it merged. Eight generated sample blocks are regenerated (npm run link:samples), and the two links resources/deprecations.md writes by hand, to Z2UI5_CL_SMP_APP_507 and _509, are repointed: no generator touches those. Two generated artefacts that were already stale on main come along: the cs_event-store_data paragraph missing from api.md and client-api.json, and the retitled Z2UI5_CL_SMP_APP_059 row in cookbook/model/tables. The commit carrying them was pushed to #319's branch minutes after that pull request had merged, so it did not go in with it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the deprecations documentation to provide clearer guidance on the recommended JSON handling approach for applications using z2ui5.
Summary
Replaces vague reference to a released JSON parser with explicit documentation of the intended JSON handling pattern: manual string composition in ABAP using
_bind()for output, and simple string operations (find/substring_before) for input parsing.Key changes
z2ui5_cl_ui5_jsonas a recommended parserjson = abap_truefind/substring_beforeto extract needed fieldsImplementation details
This change reflects the framework's design philosophy of keeping JSON handling simple and explicit rather than providing abstraction layers. The documentation now accurately represents the intended usage pattern for applications.
https://claude.ai/code/session_019rmo8XKoBEpBRZ2TZMUQrF