Fix top-level documentation - #259
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
5ddc016 to
9ce6f8b
Compare
a93ffe4 to
a2cfdcf
Compare
a2cfdcf to
3f1b071
Compare
3f1b071 to
1a54b8b
Compare
1a54b8b to
2796b1d
Compare
2796b1d to
33c8772
Compare
3ce7854 to
ec6433c
Compare
ec6433c to
db2c377
Compare
db2c377 to
2092f73
Compare
2092f73 to
6af93d4
Compare
There was a problem hiding this comment.
A component's architecture describes how it is constructed from subcomponents. Since this component contains no subcomponents, this content should be moved to the detailed design section.
There was a problem hiding this comment.
file_output_backend and datarouter_backend are not shown in this diagram
| ===================== | ||
|
|
||
| .. comp:: Logging Component | ||
| :id: comp__mw_logging |
There was a problem hiding this comment.
Should mw_looging be the final component name? I thought we wanted to use log_backend in the logging repo and 'log' in the baselibs repo.
There was a problem hiding this comment.
No. baselibs will have one dependable_element in which mw::log will be part of.
So we keep mw_log in score_logging and create a safety plan here.
in baselibs a sefetyplan will forward aous and link the score_logging safety plan
There was a problem hiding this comment.
That means we will have three components in the logging feature
- log in baselibs
- mw_log in logging
- datarouter in logging
right ? In the safety artifacts we working with references . That means the safety artifact for log (baseline) includes only an reference to mw_log (logging)
There was a problem hiding this comment.
The template https://github.com/eclipse-score/module_template/blob/main/score/component_example/docs/index.rst is not applied
There was a problem hiding this comment.
file shall be moved to ./mw_log/requirements/
See folder structure under <component_name>/ https://eclipse-score.github.io/score/main/contribute/general/folder.html
There was a problem hiding this comment.
Shall we add a folder _assets for that ?
There was a problem hiding this comment.
content shall be moved to docs/manuals/
|
|
||
| .. comp:: Data Router | ||
| .. comp:: Datarouter | ||
| :id: comp__data_router |
There was a problem hiding this comment.
component id shall be 🆔 comp__datarouter due to folder name datarouter
There was a problem hiding this comment.
| Runtime plugin loading remains experimental and is not a supported | ||
| production capability. | ||
|
|
||
| .. uml:: mw_log_repository_boundary.puml |
There was a problem hiding this comment.
this belongs to the feature architecture . Feature architecture has to be modeled in sphinx needs
| written is less then requested. | ||
|
|
||
|  | ||
| <img alt="SlotDrainerActionDiagram" src="https://www.plantuml.com/plantuml/proxy?src=https://raw.githubusercontent.com/eclipse-score/baselibs/refs/heads/main/score/mw/log/design/slot_drainer_action_diagram_design.puml"> |
There was a problem hiding this comment.
will be fixed after fixed in baselibs.
There was a problem hiding this comment.
The file shall be included as reference to detailed design or there should be folder on the rendered website design decisions
There was a problem hiding this comment.
file_output_backend and datarouter_backend are not shown in this diagram
| ### Process structure | ||
|
|
||
| [context-highlevel](uml/context-highlevel.puml) | ||
| <img alt="CONTEXT_HIGHLEVEL" src="https://www.plantuml.com/plantuml/proxy?src=https://raw.githubusercontent.com/eclipse-score/logging/refs/heads/main/score/datarouter/doc/design/uml/context-highlevel.puml"> |
There was a problem hiding this comment.
Diagramm shows an Adptive Autosar ECU
| @@ -50,9 +50,9 @@ The following constraints influenced the logging infrastructure design: | |||
| ## Context | |||
|
|
|||
There was a problem hiding this comment.
chapter could be copied/moved to feature description
6af93d4 to
846aa81
Compare
| | `project_config.bzl` | Project-specific metadata for Bazel macros | | ||
| | `LICENSE.md` | Licensing information | | ||
| | `CONTRIBUTION.md` | Contribution guidelines | | ||
| ## 📂 Key Files |
There was a problem hiding this comment.
I would remove that, usless
|
|
||
| --- | ||
|
|
||
| ## ⚙️ `project_config.bzl` |
There was a problem hiding this comment.
would remove all that below for project_config.bzl
| @@ -35,84 +30,55 @@ It provides a **standardized project structure**, ensuring best practices for: | |||
| ### 1️⃣ Clone the Repository | |||
846aa81 to
5bcf0bf
Compare
5bcf0bf to
27baea8
Compare
- Adds high-level overview of the mw::log decomposition - Remove outdated documentation - Restructure documentation to where it fits
- Fixes .puml rendering
- Replace duplicated content with redirection to single source that resides next to source code rendered by Sphinx
- Reflect score folder structure guideline - Adds high level architecture documentation and references related diagrams
27baea8 to
2ddff51
Compare
| :safety: ASIL_B | ||
| :safety: QM | ||
| :status: valid | ||
| :implements: logic_arc_int__logging__logging |
There was a problem hiding this comment.
comp__datarouter don't implement logic_arc_int__logging__logging.
This interface is implemented by mw_log.
- Feature logging defines logic_arc_int__logging__buffer
- mw_log implements logic_arc_int__logging__buffer
- datarouter uses logic_arc_int__logging__buffer
See rendered documentation here:
#259 (comment)
Fix top-level documentation