-
Notifications
You must be signed in to change notification settings - Fork 16
add component to requirement for future fix of meta model #524
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
base: main
Are you sure you want to change the base?
Changes from all commits
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 |
|---|---|---|
|
|
@@ -44,6 +44,7 @@ Component Requirements | |
| :safety: ASIL_B | ||
| :satisfies: feat_req__feature_name__some_title | ||
| :status: invalid | ||
| :belongs_to: comp__component_name_template | ||
|
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. Seems related to here, #515, first time introduce belogns_to, now in templates, and will be there anothr PR to add it to the process requirements, If would expect, that such a major chang is introduced in ONE PR, otherwise it is really difficult to follow that up
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. No, that's comes with the update of the meta model in december. The update of the picture is only for introduction of the logic interfaces in the picture which are there since a long time. See https://github.com/eclipse-score/docs-as-code/pull/331/files for introduction of the belongs_to.
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. Do not see any process requirements for that?
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. It is gd_req__arch_linkage_requirement. For that check this is necessary. Also the building block view requests that by "has". |
||
|
|
||
| The Component shall do xyz to another component to bring it to this condition at this time | ||
|
|
||
|
|
||
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.
This is only a temporary solution, I guess?
Uh oh!
There was an error while loading. Please reload this page.
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.
Yes. The infrastructure community have decided to make official releases only from time to time and in between to use this possibility to go to later commits on the other repo. In the moment, when a new release is made, which contains the previous (and the mentioned) commits, this have to be removed and the next release have to be used in the bazel dep above instead. But currently the necessary change is after 2.3.2/2.3.3. Therefore this is the way the infrastructure team have proposed. Anyway I have set the version to 2.3.3, so the diff to the git override commit is smaller.