feat: Use package name for product ORD IDs.

[ductaily]

Addressing

• ORD namespace (used as prefix in several ORD IDs) = package.name.replace(/@/,'').replace(/\//g,’'), unless explicitly configured in cds.env.ord.namespace
• Products:
  • "ordId": "customer:product:capire.bookstore:”→ i.e. package.name.replace(/@/,'').replace(/\//g,'.')
  • "vendor": "customer:vendor:customer:”
  • "title": “capire bookstore”→ i.e. package.name.replace(/@/,'').replace(/\//g,' ')
  • "shortDescription": “capire bookstore" → i.e. package.name.replace(/@/,'').replace(/\//g,' ') - Description for + "package name"

from #38

[RoshniNaveenaS]

Scenario:
Removing the sample .cdsrc JSON configuration for ord namespace and asyncapi namesapce,
The packageJSON name has special characters ( for example @cap-js/ordsample) the special character gets added and the namespace becomes cap-jsord for which the validator throws an error.
The special characters are also to be escaped here

[RoshniNaveenaS]

Here if the title and short description are same the validator throws an error.
@Fannon you could help us better too to decide what to we do about this.

[Fannon]

Here if the title and short description are same the validator throws an error. @Fannon you could help us better too to decide what to we do about this.

This rule will only cause issues when publishing to the Business Accelerator Hub, if you just have sap:core:v1 or none as policyLevel, it does not apply.

But I think it would still be better to avoid this problem in the first place, so if SAP collagues use this plugin, they don't have to rework. Maybe we can prefix the shortDescription with something like CAP application ? In the end, the shortDescription and description should be explicitly provided when publishing, so something more meaningful can be put there.

[RoshniNaveenaS]

Tested and looks good!