-
Notifications
You must be signed in to change notification settings - Fork 25
Feature Request: JSON Parser #822
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?
Feature Request: JSON Parser #822
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-check Status: Click to expand output
|
2fb2df2
to
29b929c
Compare
Security Impact | ||
=============== | ||
|
||
The module will likely work with input and output streams. |
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.
so what is the impact? Access Control needed?, please set also tag security to yes
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.
For access control and manipulation prevention (e.g. dm-verity) the hosting process and system configuration need to take care of it.
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.
then may add this as assumption of use in the feature request, otherwise it get lost, by the way, this is more a component_request as part of feature:baselib
The created documentation from the pull request is available at: docu-html |
5c9e3a9
to
70d0134
Compare
Signed-off-by: Alexandru Iulian <iulian.alexandru@continental-corporation.com>
Signed-off-by: Alexandru Iulian <iulian.alexandru@continental-corporation.com>
Co-authored-by: rattenking52 <acc.rattenking52@icloud.com> Signed-off-by: Alexandru Iulian <iulian.alexandru@continental-corporation.com>
Signed-off-by: Alexandru Iulian <iulian.alexandru@continental-corporation.com>
Co-authored-by: rattenking52 <acc.rattenking52@icloud.com> Signed-off-by: Alexandru Iulian <iulian.alexandru@continental-corporation.com>
Signed-off-by: Alexandru Iulian <iulian.alexandru@continental-corporation.com>
Co-authored-by: rattenking52 <acc.rattenking52@icloud.com> Signed-off-by: Alexandru Iulian <iulian.alexandru@continental-corporation.com>
70d0134
to
0684f44
Compare
Co-authored-by: Jonas Lammers <161199397+lammjo@users.noreply.github.com> Signed-off-by: Alexandru Iulian <iulian.alexandru@continental-corporation.com>
8c08309
to
70b96a9
Compare
:id: doc__json | ||
:status: valid | ||
:safety: ASIL_B | ||
:tags: contribution_request, feature_request |
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.
contribution_request is deprecated, shall be removed, further this is more a component_request for the baselib (feature)
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 agree that the JSON lib should be a component request. It also means that this file has to follow the https://eclipse-score.github.io/score/main/process/process_areas/change_management/guidance/change_management_component_template.html I.e. Feature flag section is not needed for a component.
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 updated that tag to component_request and removed the Feature flag section in the last commit
:satisfies: stkh_req__communication__json_library | ||
:status: valid | ||
|
||
The JSON library shall support safe communication up to ASIL-B. |
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.
so why not link to that requirement stkh_req__communication__safe
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.
stkh_req__communication__safe is ASIL-D, while this feature is meant to go only up to ASIL-B
:rationale: tbd | ||
:status: valid | ||
|
||
The software platform shall provide a JSON-Library with parsing functionality. |
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.
Does this no derive from stkh_req__functional_req__safe_config?
Signed-off-by: Alexandru Iulian <iulian.alexandru@continental-corporation.com>
Provides a proposal for a safe JSON parser feature.