Skip to content

Conversation

@RolandJentschETAS
Copy link
Contributor

Switch lifecycle to new docs as code version

@github-actions
Copy link

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

@github-actions
Copy link

The created documentation from the pull request is available at: docu-html

Copy link
Contributor

@MaximilianSoerenPollak MaximilianSoerenPollak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some comments regarding options

Copy link
Contributor

@MaximilianSoerenPollak MaximilianSoerenPollak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just this last thing that I saw / noticed.

Other than that looks good to me, thanks for the addition.

:status: valid
:safety: ASIL_B
:security: NO
:includes: logic_arc_int__lifecycle__controlif, logic_arc_int__lifecycle__alive_if
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Docs-as-code as well as process currently state that 'comp_arc_sta' can only have 'comp' and 'comp_arc_sta' inside of the includes attribute

The build still succeeds as currently optional links are not checked / enforced to be correct.
Though this will stop working once that is enforced.

I guess uses or implements or fulfils are allowed to have 'logic_...' needs linked inside of it.

Copy link
Contributor Author

@RolandJentschETAS RolandJentschETAS Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. I'm not sure if that is intended ore an fault of the process and docs as code as well.

If components are structured internally into (sub)components, then it should be identically to the feat via the interfaces of the sub components. Will discuss this in the process community.

Currently the draw function for components works exactly in this way with the interfaces.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be something that should be brought up in the Process meeting then

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. I have done it. Until, I have removed the interfaces. Makes no sense anyway because of there is no internal substructuring defined.

Copy link
Contributor

@MaximilianSoerenPollak MaximilianSoerenPollak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems good as far as I can tell.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants