From d7a18e87e701d6ae10dd5fe9436fa82e7fd8ae5b Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 10 Oct 2026 19:20:41 +0000 Subject: [PATCH] docs: bring README.md back in line with abap2UI5's frontend/common/README.md The shared-file gate in abap2UI5 holds this file byte-identical to its frontend/common/README.md and has been red since the z2ui5_ccc link moved to abap2UI5-addons/custom-controls-customer there (#2874) without this copy following; #2877 added the renamed-backend branch spelling (standard___) to the same paragraph. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_015HdEPygSFbUBzVdWBJ5Ugi --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b0dd837d..b82e3c4f 100644 --- a/README.md +++ b/README.md @@ -53,7 +53,7 @@ Because the overwrite is not loud — the change is merged, works, and vanishes #### Renaming -Need the BSP under a **different name** (e.g. a second copy in the same system)? Run the [`frontend_deploy` workflow](https://github.com/abap2UI5/abap2UI5/actions/workflows/frontend_deploy.yaml) in abap2UI5 with a branch name of the form `standard_` — plain (`ZMYUI5`) or in a registered namespace (`/ABAPGIT/` → BSP `/ABAPGIT/UI5`, handler `/ABAPGIT/CL_LP_HANDLER`) — it generates and pushes a branch `standard_` / `standard_v2_` with the whole deployment identity (BSP, SICF nodes, handler class) renamed. Details in [`tools/bsp_rename`](https://github.com/abap2UI5/abap2UI5/tree/main/tools/bsp_rename). +Need the BSP under a **different name** (e.g. a second copy in the same system)? Run the [`frontend_deploy` workflow](https://github.com/abap2UI5/abap2UI5/actions/workflows/frontend_deploy.yaml) in abap2UI5 with a branch name of the form `standard_` — plain (`ZMYUI5`) or in a registered namespace (`/ABAPGIT/` → BSP `/ABAPGIT/UI5`, handler `/ABAPGIT/CL_LP_HANDLER`) — it generates and pushes a branch `standard_` / `standard_v2_` with the whole deployment identity (BSP, SICF nodes, handler class) renamed. For a backend that was itself renamed with the [`build-rename` workflow](https://github.com/abap2UI5/abap2UI5/actions/workflows/build-rename.yaml), append `__` (`standard_#abap2ui5#__#abap2ui5#`): the handler then calls that backend's `cl_http_handler`. Details in [`tools/bsp_rename`](https://github.com/abap2UI5/abap2UI5/tree/main/tools/bsp_rename). #### Sibling BSPs @@ -62,7 +62,7 @@ Need the BSP under a **different name** (e.g. a second copy in the same system)? | resourceRoot | Sibling BSP | Built from | |---|---|---| | `z2ui5_cci` | `Z2UI5_CCI` | [abap2UI5-addons/custom-controls](https://github.com/abap2UI5-addons/custom-controls) — community custom controls | -| `z2ui5_ccc` | `Z2UI5_CCC` | [abap2UI5/customer-frontend-extension](https://github.com/abap2UI5/customer-frontend-extension) — a customer's own reuse library, icon font or CSS | +| `z2ui5_ccc` | `Z2UI5_CCC` | [abap2UI5-addons/custom-controls-customer](https://github.com/abap2UI5-addons/custom-controls-customer) — a customer's own reuse library, icon font or CSS | Neither BSP has to be installed: the browser requests nothing from a resourceRoot until a view names the namespace. Both entries come from abap2UI5 `app/webapp` — see "Where to change what" above.