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

TBI - Prohibit non-CAP Fiori generation into a CAP project folder #2427

Open
korotkovao opened this issue Oct 1, 2024 · 0 comments
Open
Assignees

Comments

@korotkovao
Copy link
Contributor

As a Fiori developer, I want to be alerted and prevented from generating a Fiori application into a CAP project folder unless I have chosen the Local CAP Project as my data source.

Description

Currently the application generator allows users to create a non-CAP Fiori application inside of a CAP project. This is not supported by our tooling and has caused some customer support issues.

Design

Interaction

User launches the generator and chooses a data source that is not Local CAP Project.
On the project attributes step, user provides a project folder that is part of an existing CAP project.
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.

Acceptance Criteria

Given I attempt to use a project folder for my Fiori application that is part of an existing CAP project, and my Fiori application isn't using the Local CAP Project data source option for this CAP project, then I will be prevented from continuing with the following error 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.

Notes

When you choose Local CAP Project as your data source, you don't have an option to choose the project folder, it will always be generated in the correct location.

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