Open RamIndia opened 1 month ago
TODO: Check-mark the check-boxes given in the issue body (only) after merging the related pull requests. Related PRs: #42 && #43 cc: @ductaily @Fannon @RoshniNaveenaS
Regarding the Don’t add a suffix if I already specified a .json suffix in the -o / —dest parameter
:
The fix should be implemented in the cds-dk repo, not in the ord plugin.
Compiler is always attaching the suffix that is equal to the -to
parameter value.
Check by running e.g. : cds compile srv/services.cds -2 csn -o ORD15.someext
=> Result is: ORD15.someext.csn
(or -2 SQL)
@RoshniNaveenaS @ductaily @Fannon
The same as above stands for Use .ord.json as file suffix instead of .ord if not
.
Check-marked both issues because the fix shall not be done in cap-js/ord plugin.
@RoshniNaveenaS @ductaily @Fannon
Regarding the
Don’t add a suffix if I already specified a .json suffix in the -o / —dest parameter
: The fix should be implemented in the cds-dk repo, not in the ord plugin. Compiler is always attaching the suffix that is equal to the-to
parameter value. Check by running e.g. :cds compile srv/services.cds -2 csn -o ORD15.someext
=> Result is:ORD15.someext.csn
(or -2 SQL)@RoshniNaveenaS @ductaily @Fannon
@stewsk: As of now cds compile -2 always appends the extension, can we ignore appending the format if extension is specified in the -o parameter?
@aramovic79 @Fannon
The issue regarding Don’t add a suffix if I already specified a .json suffix in the -o / —dest parameter
will be resolved in cds-dk 8.2.0. See corresponding issue: https://github.tools.sap/cap/issues/issues/16685
@zongqichen @ductaily : I've checked marked items that are done. I'm not sure for the remaining. Could you please take a look and check-mark the finished ones? Thanks!
Hi @aramovic79, I marked the Jest and CICD pipeline item. I think we basically introduced the test and action as pipeline.
Please find attached the ord documents we walked through in our review:
Here are the changes decided for the ORD document :
"$schema": "https://sap.github.io/open-resource-discovery/spec-v1/interfaces/Document.schema.json"
package.name.replace(/@/,'').replace(/\//g,’')
, unless explicitly configured in cds.env.ord.namespaceproducts
"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,' ')groups
"title": "Catalog Service”
→ i.e. without appending “ Title”packages
package.name.replace(/@/,'').replace(/\//g,'.')
"partOfProducts": [ "customer:product:capire.bookstore:” ]
→ has to be the same as the product name in the products section"vendor": "customer:vendor:customer:”
→ has to be the same as the vendor in the products section"title": "capire bookshop”
→ take what is there, don’t add extra text like “sample title for"“shortDescription"
→ take what is there, don’t add extra text like “Here’s the short description for ..."“description"
→ take what is there, don’t add extra text like “Here’s the short description for ..."consumptionBundles
apiResources
"title": "Catalog Service”
→ take what is there, don’t add extra text like “The service is for ..."“shortDescription": "Catalog Service”
→ take what is there, don’t add extra text like “Here we have the shortDescription for ..."“description": "Catalog Service”
→ take what is there, don’t add extra text like “Here we have the description for ...""partOfPackage": "customer.capirebookstore:package:capire.bookshop:v1”
→ correct namespace prefix in package ref - use appName as packageName as a fallbackeventResources
Explanation:
Tests