Skip to content

Pass text values through t, and render app 483's launchpad flag through b - #71

Merged
oblomov-dev merged 3 commits into
mainfrom
claude/abap2ui5-concept-review-bsgapy
Sep 12, 2026
Merged

oblomov-dev merged 3 commits into
mainfrom
claude/abap2ui5-concept-review-bsgapy

Conversation

@oblomov-dev

@oblomov-dev oblomov-dev commented Sep 12, 2026

Copy link
Copy Markdown
Member

What this changes

Two things, two commits:

  1. Text values through t. Every attribute value whose origin is data moves from a( v = … ) onto a( t = … ): 15 attributes in the overview app (tile texts, hints, icons, CSS classes, the tooltip href) and app 010 (|Edit Travel { s_draft-travel_id } (Draft)|). t is the new third value form of z2ui5_cl_ui5_view_builder=>a( ) (Let a( ) take text through t so data in a view attribute is escaped by the builder abap2UI5#2732): the builder applies escape_literal( ) to it, so a brace or backslash in the value is shown instead of parsed by UI5 as a binding. Not a rename with identical behaviour — that is why constants, bindings and events stay on v.

  2. A bug in app 483. visible was fed client->get( )-check_launchpad_active, an abap_bool, through v — it reached the view as visible="X", which UI5 refuses for a boolean property, so both launchpad buttons showed wherever the app ran. It goes through b now, which renders true/false.

Why

A data value written through v is a binding to UI5 when it carries a brace. The linter rule unescaped-text-in-attribute (abap2UI5/linter#102) reports the remaining v values with data — 0 on this branch.

Checks

  • abaplint against the framework branch: 0 findings (main resolution keeps CI red on lint until #2732 lands — this PR after that one)
  • npm run check:abap2ui5: 32 files, 0 failing
  • check:overview, check:keywords, check:abapdoc, check:samples-md, check:catalogue, check:app-rules, check:prose, check:derived: OK

🤖 Generated with Claude Code

https://claude.ai/code/session_01SzFGoLSjycYRD1zvvxqRVJ

claude and others added 3 commits September 12, 2026 10:40
check_launchpad_active is an abap_bool, and written through v it reached
the view as visible="X" - a value UI5 refuses for a boolean property, so
both buttons showed regardless of where the app ran. b renders true/false.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SzFGoLSjycYRD1zvvxqRVJ
The framework's view builder takes text through a( t = ) now: the value
is escaped as a literal, so a brace or backslash in it is shown instead of
parsed as a binding. Every attribute value whose origin is data - a
template that interpolates, a record field, an event argument, a text
variable, a name-and-literal chain - moves onto t; constants, bindings,
events and expressions stay on v, where the builder writes them as they
are. Needs abap2UI5 with the t parameter of z2ui5_cl_ui5_view_builder=>a( ).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SzFGoLSjycYRD1zvvxqRVJ
@oblomov-dev
oblomov-dev merged commit 6444b94 into main Sep 12, 2026
9 of 11 checks passed
@oblomov-dev
oblomov-dev deleted the claude/abap2ui5-concept-review-bsgapy branch September 12, 2026 10:54
@oblomov-dev oblomov-dev changed the title Use typed attributes (t/b) instead of generic (v) in XML generation Pass text values through t, and render app 483's launchpad flag through b Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants