add support for exclude annotations as part of app gen

[kjose90]

#1949

• Added logic in fiori-elements-writer to not add local annotations when excludeAnnotations is true
• Added option excludeAnnotations to FioriElementsApp type in fiori-elements-writer
• Added a test to odata-service-writer which generates project when no service annotations are provided

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 5c8fd13449a429f59688aeaa98c91efb311a5a05

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
88.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[tobiasqueck]

@kjose90 if understand it correctly then this is for CAP, so I was wondering if it makes more sense to add an option of the annotation format instead of excluding annotations because you would want an annotation.cds file in CAP, correct?

[kjose90]

@kitzkan if understand it correctly then this is for CAP, so I was wondering if it makes more sense to add an option of the annotation format instead of excluding annotations because you would want an annotation.cds file in CAP, correct?

Thanks @tobiasqueck. We have revised our plan and will add an option to add annotation.cds file if app is CAP 👍

[kjose90]

Closing this PR as a revised plan is going to be implemented. The decision was made to write annotation.cds for CAP applications.