Thank you for the contribution.
However, I don’t think this is the correct approach for this.
If the E2E npm script should only be present when an application is added to the application, then I think that the application schematic should be adding it. This allows the workspace schematic to remain agnostic to the concept of an application.

I also, do agree with @clydin

I agree that it's a valid point raised, I did it because I thought to treat it the same as the minimal flag.

I will push a commit later with the changes.
So the workspace schematic won't have the e2e script, but it will be added via the application schematic, right? Or does the workspace schematic remain as is, and will the application schematic remove the e2e script if needed?

I think the former (removing it from the workspace generation) would be the appropriate path.

Should this be part of the e2e schematic instead?

Hi, @timdeschryver, sorry for taking us long to get back to you about this.

Should this be part of the e2e schematic instead?

Yes, I think that's the best approach.

Should be ready for another review @alan-agius4
If there's something I can do, please let met know.

Hi @timdeschryver, sorry for the delay on this. I rebased the PR and did some changes to get this in!

Thanks and sorry once again.

@alan-agius4 no need to say sorry.
Thanks for the help!

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}