Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG - incorrect error message for non-CAP generation into a CAP project folder that contains Fiori app(s) #2456

Open
2 of 3 tasks
korotkovao opened this issue Oct 11, 2024 · 0 comments
Assignees

Comments

@korotkovao
Copy link
Contributor

korotkovao commented Oct 11, 2024

Related Feature

#2427

Description

When non-CAP Fiori app is generated into a CAP project folder with pre-existing Fiori apps, incorrect error message is shown.

Steps to Reproduce

  1. Clone or copy CAP Java project from https://github.com/SAP-samples/cloud-cap-samples-java/
  2. Launch Fiori generator and choose a data source that is not Local CAP Project
  3. On Project Attributes step, provide as Project folder path an app folder that is part of sample CAP Java project

Expected results

User is prevented from continuing with the following message: The selected project folder is part of an existing CAP project. This application must therefore use the local CAP project as the data source

Actual results

User is prevented from continuing with the following message: The project folder path already contains an SAP Fiori application in the folder: c:\SAPDevelop\New\cloud-cap-samples-java-main\app. Please choose a different folder and try again.

Screenshots

image

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}

@korotkovao korotkovao self-assigned this Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant