You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -38,7 +38,7 @@ To activate this feature, use the following feature flag:
38
38
Abstract
39
39
========
40
40
41
-
This feature request proposes the integration of a safe JSON parser.
41
+
This feature request proposes the integration of a safe JSON-Library with parsing functionality.
42
42
43
43
44
44
Basic Functionality
@@ -55,13 +55,13 @@ Motivation
55
55
==========
56
56
57
57
S-CORE is targeting high-performance automotive systems with safety impact.
58
-
Some applications, like the IPC communication solution, require a safe JSON parser to enable loading of configuration information at runtime.
58
+
Some applications, like the IPC communication solution, require a safe JSON-Library with parsing functionality to enable loading of configuration information at runtime.
59
59
There is currently no solution for this inside S-CORE.
60
60
61
61
Rationale
62
62
=========
63
63
64
-
A JSON parser needs to be introduced in S-CORE software platform due to specific functional dependencies of different features (ex: IPC).
64
+
A JSON-Library with parsing functionality needs to be introduced in S-CORE software platform due to specific functional dependencies of different features (ex: IPC).
65
65
66
66
Further details are available in the following section:
67
67
.. _Specification:
@@ -74,7 +74,7 @@ The following details and requirements describe the aspects of current feature i
74
74
General considerations
75
75
----------------------
76
76
77
-
The JSON parser should provide read and data conversion capabilities:
77
+
The JSON-Library should provide parsing and data conversion capabilities:
78
78
79
79
:need:`feat_req__json__validation`
80
80
:need:`feat_req__json__deserialization`
@@ -99,8 +99,7 @@ Full testability for the public API
99
99
----------------------------------------
100
100
101
101
Our users will be required to proof certain coverage metrics, like line coverage or branch coverage.
102
-
For them to reach full coverage, they need to be easily able to mock or fake parts of the JSON functionality in their
103
-
unit tests.
102
+
For them to reach full coverage, they need to be easily able to mock or fake the public API of the JSON-Library in their unit tests.
0 commit comments