Skip to content

Conversation

@linnealinnea
Copy link
Contributor

@linnealinnea linnealinnea commented Dec 17, 2025

Adapting json architecture doc to include vajson as a new json backend and adding component requirements. Related to #2310.

Adapting json architecture doc to include vajson as a new backend and adding component requirements.
    Dummy commit to report author details.

    Also-by: Linnea Bennerhed <linnea.bennerhed@vector.com>
@linnealinnea linnealinnea changed the title Issue 2310 - Component request: (JSON parsing) VaJson in S-CORE docs: Adding requirements for vajson Dec 17, 2025
@linnealinnea linnealinnea marked this pull request as ready for review December 17, 2025 13:38
@linnealinnea linnealinnea requested a review from a team as a code owner December 17, 2025 13:38
@linnealinnea linnealinnea marked this pull request as draft December 17, 2025 13:39
@masc2023
Copy link
Contributor

Copy link
Contributor

@FScholPer FScholPer left a comment

Choose a reason for hiding this comment

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

Needs agreement in architecture community. Do we have something like that for vajson?

Fix Sphinx RST build issues.

Also-by: Linnea Bennerhed <linnea.bennerhed@vector.com>
Fix requirement linking.

Also-by: Linnea Bennerhed <linnea.bennerhed@vector.com>
Issue 2310 - Component request: (JSON parsing) VaJson in S-CORE

Fix indenting.

Also-by: Linnea Bennerhed <linnea.bennerhed@vector.com>

Signed-off-by: Linnea Bennerhed <72805813+linnealinnea@users.noreply.github.com>
@github-actions
Copy link

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

@linnealinnea
Copy link
Contributor Author

@FScholPer The component was accepted in the baselib FT MeetingNotes, and my understanding is that @4og will bring this up on next architecture community meeting after Christmas.

@linnealinnea linnealinnea changed the title docs: Adding requirements for vajson docs: Adding requirements and a component change request for vajson Dec 18, 2025
@thilo-schmitt
Copy link

@linnealinnea thank you for your PR and great to hear that it is already aligned in the Feature Team. Let's, however, get the buy-in from the Architecture Community also. We have to make sure that we uphold our principle "one solution only for any given aspect", which is watched over by the Architecture Community.

Adding first version of "Change Management Component Request"
linnealinnea

This comment was marked as outdated.

@linnealinnea
Copy link
Contributor Author

Keeping the PR in draft mode until next Architecture Community round

# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************

.. _component_template:
Copy link
Contributor

Choose a reason for hiding this comment

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

you can remove that or replace by reference you need for your specific component

:safety: ASIL_B
:security: NO
:realizes: wp__cmpt_request
:tags: contribution_request, feature_request
Copy link
Contributor

Choose a reason for hiding this comment

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

it seems a component_request, not new feature?

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.

4 participants