[Bug]: Generating an app/lib with a scope leads to unexpected behaviour

[malek-benazzouz]

Package name

core

Package version

11.5.3

Reproduction steps

Create a project with @o3r/create, then generate an app and a lib with a scope:

npm create @o3r project
ng g application @scope/app
ng g library @scope/lib

Current result

1. My app is created under folder apps/scope-app.
2. My lib is created under folder libs/scope-lib.
3. The following error is raised during the ng g library @scope/lib step:

No application detected, the Otter environment will not be setup
No application detected, the environment can not be generated

This error is not raised if I run the same scenario but without giving a scope (e.g., if I run ng g application app).

Expected result

1. My app should be created under folder apps/app.
2. My lib should be created under folder libs/lib.
3. No error during the ng generate steps.

Additional comments

I specified that the impacted package is core because that is where the error logging is done, but the issue root cause may be in an other package.

[kpanot]

Hi,

Thank you for the report.
I do not know if we want to remove the scope from the generated path. If do so, we won't be able to generate 2 packages with the same name but different scope.

[kpanot]

This issue will lead to the following:

• Discussion regarding the folder to generate when a scope is specified
• Bug fix of the generators