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
Where an odata service url prompt is used a best effort attempt is made to retrieve annotations (assuming the service is hosted on an Abap system). Annotations are not retrieved.
Steps to Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected results
Actual results
Screenshots
If applicable, add screenshots to help explain the problem.
Version/Components/Environment
Add any other context about the problem here
OS:
Mac OS
Windows
Other
Root Cause Analysis
Problem
{describe the problem}
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:
IainSAP
changed the title
BUG - odata-service-inquirer: Annotations not returned for odata service urls
BUG - odata-service-inquirer: Annotations not returned for (Abap hosted) odata service urls
Aug 31, 2024
…using service url prompt (#2310)
* fix for annotations not retrieved using service url prompt
#2309
* Update jest.config.js
* Adds cset
---------
Co-authored-by: J Long <[email protected]>
Description
Where an odata service url prompt is used a best effort attempt is made to retrieve annotations (assuming the service is hosted on an Abap system). Annotations are not retrieved.
Steps to Reproduce
Steps to reproduce the behavior:
Expected results
Actual results
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
{describe the problem}
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: