Bring the site to @cap2ui5/cds-plugin 0.4.0 - #36
Merged
Merged
Conversation
0.4.0 is on npm since 2026-09-30 and pins runtime 1.146.0; @cap2ui5/samples 0.2.0 needs it (peer ^0.4.0). The site still named 0.3.1, 1.145.0 and ^0.3.x - so check on main went red against cap2UI5 main - and described 0.3's behaviour where 0.4.0 changed it: - Only a field the app binds is sent to the browser and taken back from it; every field is still kept in the draft. The app interface, data binding, persistence and migration pages said every field is model. - defineApp refuses a camelCase field, a #private member and a name the runtime already has a class of. The selection-screen example declared minTotal and onlyOpen, which 0.4.0 refuses; they are min_total and only_open now. - Runtime 1.146.0 carries abap2UI5#2802, the X-CSRF-Token handshake, so the route `cds add approuter` generates works as it is. The deployment page says so and keeps the extra route for 0.3.x; troubleshooting and the roadmap follow. That is read from the frontend's and approuter 23.0.0's code - without XSUAA or IAS here it was not run end to end, and the page says that too. - configuration documents compression and accelerate, and a short Performance section (the runtime's accelerations, Node 24). - A package's apps get one startup line, not one each. verify-refs read the pinned runtime from runtime/package.json, the repository's stand-in, which still says 1.145.0 - so every stale 1.145.0 here passed. It now reads the exact @abap2ui5/node-runtime dependency of plugin/package.json, what a reader installs. Historical mentions no longer name the old number, rather than allowlisting it. The unscoped cap2ui5 is a deprecated placeholder on npm since 2026-09-30 (cap2UI5/cap2UI5#97), not withdrawn: the pages, AGENTS.md and verify-refs' messages say so (was the draft docs#33). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NwpbkojNzGmuJrFdbwo5JF
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.
@cap2ui5/cds-plugin0.4.0 has been on npm since 2026-09-30 and pins@abap2ui5/node-runtime1.146.0.@cap2ui5/samples0.2.0 needs it (peer^0.4.0). The site still said 0.3.1, 1.145.0 and^0.3.x, socheckagainst cap2UI5 main fails on main. It also described 0.3 behaviour that 0.4.0 changed. Source: cap2UI5/cap2UI5plugin/CHANGELOG.md(0.4.0) andplugin/README.md. This PR includes and supersedes the draft #33.What changes
Versions
"^0.4.0"in the deployment dependency and in the peer-dependency example.Behaviour 0.4.0 changed
defineApprefuses: camelCase fields (isAdmin→is_admin),#privatemembers, and a name the runtime already has a class of. The selection-screen example declaredminTotal/onlyOpen, which 0.4.0 refuses; it now usesmin_total/only_open.X-CSRF-Tokenhandshake. The deployment section is now "The approuter and its CSRF token": the generated catch-all route works as it is, and the extra route stays in a box for 0.3.x. Troubleshooting, roadmap and HANDOVER.md follow.@abap2ui5/node-runtime@1.146.0(on 403 withRequired:HEADwithX-CSRF-Token: Fetch, then retry) and againstxsrf-token-handler.jsin approuter 23.0.0. A local approuter run without XSUAA does not check tokens at all, so it proves nothing. The page says it has not yet been run against XSUAA or IAS.compressionandacceleraterows and a short Performance section (the runtime's accelerations, Node 24,NODE_COMPILE_CACHE). The log example gainsruntime accelerations active.@cap2ui5/samples 71 apps - listed on CAP's start page, …), not one line per app.The unscoped
cap2ui5(from #33)0.0.1-placeholder, The unscoped cap2ui5 holds a placeholder now cap2UI5#97), not "withdrawn": nomain, and its bin prints where to go and exits 1.verify-refs
runtime/package.json, the repository's stand-in, which still says 1.145.0. So every stale 1.145.0 on the site passed.@abap2ui5/node-runtimedependency fromplugin/package.json, which is what a reader installs. With that change it found six stale mentions.z2ui5_cl_smp_app_493(the sample the quickstart names) is in.verify-refs-ignorewith its reason: it lives in abap2UI5/samples.Checks
npm run check:ciagainst cap2UI5 main (0.4.0) and abap2UI5 main: verify-refs OK, build OK.Outside this repository
cap2UI5's own
plugin/README.md→ "In production" still says "@abap2ui5/node-runtime1.145.0, the runtime this version pins, does not fetch that token yet". With 0.4.0 that is out of date.🤖 Generated with Claude Code
https://claude.ai/code/session_01NwpbkojNzGmuJrFdbwo5JF
Generated by Claude Code