-
Notifications
You must be signed in to change notification settings - Fork 38
added coverage of multiple ids in tags #553
New issue
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
Changes from all commits
2ad25b2
dc82ed2
14d0329
4b28ee8
f6ec4b7
5c3cd65
efb50b4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -708,7 +708,7 @@ To avoid conflict with the formats actual contents, you embed these definitions | |
| Tags have the following format: | ||
|
|
||
| ``` | ||
| [ <covered-artifact-type> -> <specification-object-id> ] | ||
| [ <covered-artifact-type> -> <list-of-specification-object-ids> ] | ||
| ``` | ||
|
|
||
| Spaces above were only added for readability. They are optional. In fact usually people prefer a more compact form. | ||
|
|
@@ -737,7 +737,7 @@ Examples: | |
| // [impl~validate-password~2->dsn~validate-authentication-request~1] | ||
| ``` | ||
|
|
||
| ##### Forwarding Requirements | ||
| ##### Needed Coverage | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good find. 👍 Compliance: I am guessing you are using an LLM to help with the work. Please note that according to our contribution guideline, LLM-assisted PR must state that. |
||
|
|
||
| When using UML models as design document files like UML models it is useful to add needed coverage as well. To do this, you can use the following format: | ||
|
|
||
|
|
||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Completeness: Please also add tests that the features with requiring coverage and partial spec item definition still work in combination with the comma-separated covered IDs.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That test looks good now. I think I will have to adapt the IDE plugin once this is merged. :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Davidius86 for the PR. I am started reviewing it. I will update main to 2.6.0 and create the release letter in another PR, so that we have a place where we can mention the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Completeness: Please also add a short example of the syntax to
.agents/skills/openfasttrace/SKILL.md.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Completeness: Please add an short entry for this in the change log too (we are currently working towards 4.6.0).