We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The following model definition is valid...
@Term("My HR Model") @Term_description("Reusable data definitions for the HR department.") namespace acme.hr@1.0.0
When applying the extract-decorators command
extract-decorators
concerto extract-decorators --model hr.cto --removeDecoratorsFromSource
Produces a vocabulary file:
locale: en namespace: [email protected] declarations: - : My HR Model description: Reusable data definitions for the HR department.
I would expect a vocabulary file such as this:
locale: en namespace: [email protected] term: My HR Model description: Reusable data definitions for the HR department. declarations: ...
@accordproject/concerto-vocabulary
The text was updated successfully, but these errors were encountered:
How do we setup target for setting decorator on a model namespace? My assumption was target would look like this.
{ "$class": "[email protected]", "type": "UPSERT", "target": { "$class": "[email protected]", "namespace": "[email protected]" }
But when I tried it out in code. It just applied the decorator on top of all the declarations and not on the namespace. https://replit.com/@sanketshevkar/AccordProjectConcerto-Decorator-Command-Set#index.js
Sorry, something went wrong.
@sanketshevkar can this now be closed?
No branches or pull requests
Bug Report 🐛
The following model definition is valid...
When applying the
extract-decorators
commandProduces a vocabulary file:
Expected Behavior
I would expect a vocabulary file such as this:
Possible Solution
@accordproject/concerto-vocabulary
package should be updated to support namespace-scoped decoratorsThe text was updated successfully, but these errors were encountered: