-
Notifications
You must be signed in to change notification settings - Fork 20
fix issues which prevent latest main update #349
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
c59113c
31fb7a0
3454b84
fcedae9
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 |
|---|---|---|
|
|
@@ -689,9 +689,8 @@ Architecture Attributes | |
| :parent_covered: NO: we only enable linking, we do not link | ||
| :satisfies: | ||
| gd_req__req_attr_impl, | ||
| gd_req__impl_design_code_link, | ||
|
|
||
| Docs-as-Code shall allow source code to link to needs. | ||
| Docs-as-Code shall allow source code to link to requirement sphinx-needs objects. | ||
|
|
||
| A link to the corresponding source code location in GitHub shall be generated in the | ||
| generated documentation within the linked requirement. | ||
|
|
@@ -720,14 +719,14 @@ Architecture Attributes | |
|
|
||
| Provide needs type ``dd_sta`` for static diagrams showing unit interactions as UML. | ||
|
|
||
| .. tool_req:: Dynamic Diagram for Unit Interactions | ||
| :id: tool_req__docs_dd_dyn | ||
| :tags: Detailed Design & Code | ||
| :implemented: YES | ||
| :parent_covered: YES | ||
| :satisfies: gd_req__impl_dynamic_diagram | ||
| .. .. tool_req:: Dynamic Diagram for Unit Interactions | ||
| .. :id: tool_req__docs_dd_dyn | ||
| .. :tags: Detailed Design & Code | ||
| .. :implemented: YES | ||
| .. :parent_covered: YES | ||
| .. :satisfies: gd_req__impl_dynamic_diagram | ||
|
|
||
| Provide needs type ``dd_dyn`` for dynamic diagrams showing unit interactions as UML. | ||
| .. Provide needs type ``dd_dyn`` for dynamic diagrams showing unit interactions as UML. | ||
|
Contributor
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. Commenting is not a good idea. Delete it.
Contributor
Author
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. See below |
||
|
|
||
|
|
||
| Testing | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -684,7 +684,6 @@ needs_types: | |
| includes: sw_unit, sw_unit_int | ||
| parts: 3 | ||
|
|
||
| # req-Id: tool_req__docs_dd_dyn | ||
| dd_dyn: | ||
|
Contributor
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. If there is no requirement for the dd_dyn element, shouldn't we delete it from the metamodel?
Contributor
Author
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. The problem is, that the process description of the implementation process still contains a dynamic diagram, but the process requirement is gone. So it is currently unclear if deletion of the requirement was a mistake or not. The PR is only to make overall update is running. But it don't solve the issue, that the implementation process contains undefined parts. But this is in another repo and must be fixed after discussion. |
||
| title: Dynamic detailed design | ||
| color: #FEDCD2 | ||
|
|
||
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.
I would keep this as it was, since our tool requirement intentionally did not differentiate whether its a requirement or not. The tool was more generic, then the minimum process requirement.