You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run App generator and generate a FE v4 List Report using
local CAP project cap-sflight
TraveService (NodeJS)
main entity Travel
nav entity to_Booking
choose any module name /app title/ app namespace
Expected results
Sript added to added to the root package.json.
The generated watch Script looks something like this "watch-typescript": "cds watch --open typescript/webapp/index.html?sap-ui-xx-viewCache=false"
Actual results
No new cds watch script was added to the root package.json .
Issue only occurs in SBAS and works well in VSCode.
Screenshots
If applicable, add screenshots to help explain the problem.
Version/Components/Environment
Add any other context about the problem here
OS:
Mac OS
SBAS
Root Cause Analysis
Problem
Issue with paths in SBAS when detecting the @sap/cds version.
Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}
The text was updated successfully, but these errors were encountered:
Related Feature
Feature request: issue number
Description
A clear description of what the bug is.
Steps to Reproduce
Steps to reproduce the behaviour:
Expected results
Sript added to added to the root package.json.
The generated watch Script looks something like this
"watch-typescript": "cds watch --open typescript/webapp/index.html?sap-ui-xx-viewCache=false"
Actual results
No new
cds watch
script was added to the root package.json .Issue only occurs in SBAS and works well in VSCode.
Screenshots
If applicable, add screenshots to help explain the problem.
Version/Components/Environment
Add any other context about the problem here
OS:
Root Cause Analysis
Problem
Issue with paths in SBAS when detecting the
@sap/cds
version.Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}
The text was updated successfully, but these errors were encountered: