Repository navigation
The FAQ answers what decision makers actually ask, and every in-page link lands - #20
Merged
Merged
Conversation
…link lands Six questions the research found asked and unanswered: is it an SAP product (no, and who showed it), will the next framework release break our apps (it has, and what holds now), guidelines that reject Z-objects or need a certified add-on, heavy GUI transactions and the stateful limit, several framework versions on one system, and the one clause on JavaScript skills. Claims a reader cannot check are gone: "faster than most Fiori apps", the weeks and months of the rivals' columns, "Lock-in: None". Screen Personas and SAP GUI for HTML are named where the transaction may stay as it is. A governance line says where the data stays and for how long. Two anchors on the FAQ and Community pages pointed at #who-runs-it on a page that does not carry it; a test now resolves every in-page link against the page it stands on, holds the teaser's question count to the FAQ, and checks the release number against the newest release (skipping offline). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014YZFmFZwmxFekaMfr3Ka5m
The answer on framework stability said the API churn was a 2023 and 2024 story; the manual's release notes carry BREAKING entries in 1.144 and 1.145 of 2026, where the superseded parts were removed. A reader of both pages would have caught the gap. The answer now names both and the rule that holds: frozen first, removed later, every removal marked. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014YZFmFZwmxFekaMfr3Ka5m
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
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.
Checked against the questions found in the framework's GitHub issues, SAP Community and the one independent newsletter review. These are the questions consultants raise on behalf of customers.
New FAQ questions
"Who do we call" now opens with the support ladder.
Claims a reader cannot check are gone
Added
Fixes and tests
#who-runs-iton a page that does not carry it.npm run check: 12 pass, 1 skipped (the network test in the sandbox).Generated by Claude Code