Home
last modified time | relevance | path

Searched refs:JSON (Results 1 – 25 of 286) sorted by relevance

12345678910>>...12

/openbmc/bmcweb/test/include/
H A Dhttp_utility_test.cpp21 isContentTypeAllowed("application/json", ContentType::JSON, false)); in TEST()
33 isContentTypeAllowed("application/html", ContentType::JSON, false)); in TEST()
61 std::array<ContentType, 2> htmlJson{ContentType::HTML, ContentType::JSON}; in TEST()
77 std::array<ContentType, 2> jsonHtml{ContentType::JSON, ContentType::HTML}; in TEST()
81 std::array<ContentType, 2> cborJson{ContentType::CBOR, ContentType::JSON}; in TEST()
88 ContentType::JSON); in TEST()
96 ContentType::JSON); in TEST()
102 ContentType::JSON); in TEST()
106 ContentType::JSON); in TEST()
111 ContentType::JSON); in TEST()
[all …]
/openbmc/pldm/docs/
H A Dpdr_implementation.md5 PDR information is encoded in platform specific JSON files. JSON files must be
6 named based on the PDR type number. For example a state effecter PDR JSON file
7 will be named 11.json. The JSON files may also include information to enable
11 The PLDM responder implementation finds and parses PDR JSON files to create the
13 JSON updates. New PDR type support would require JSON updates as well as PDR
15 PDR entries for that type based on the JSON, and to update the central PDR repo.
/openbmc/phosphor-power/phosphor-regulators/
H A DREADME.md6 regulators. The application is controlled by a JSON configuration file.
10 - [config_files](config_files/) contains JSON configuration files
11 - [docs](docs/) contains documentation on this application and the JSON
13 - [examples](examples/) contains examples, such as a simple JSON configuration
15 - [schema](schema/) contains schema defining the JSON configuration file format
18 - [tools](tools/) contains command line tools, such as the JSON configuration
/openbmc/phosphor-webui/app/common/services/
H A Dapi-utils.js38 console.log(JSON.stringify(error));
66 console.log(JSON.stringify(error));
87 data: JSON.stringify({'data': []})
103 var json = JSON.stringify(response.data);
104 var content = JSON.parse(json);
133 var data = JSON.stringify({
141 var content = JSON.parse(evt.data);
169 var data = JSON.stringify({
181 var content = JSON.parse(evt.data);
215 var data = JSON.stringify({
[all …]
/openbmc/phosphor-power/phosphor-regulators/test/
H A Dffdc_file_tests.cpp49 FFDCFile file{FFDCFormat::JSON}; in TEST()
52 EXPECT_EQ(file.getFormat(), FFDCFormat::JSON); in TEST()
76 FFDCFile file{FFDCFormat::JSON}; in TEST()
115 FFDCFile file{FFDCFormat::JSON}; in TEST()
124 FFDCFile file{FFDCFormat::JSON}; in TEST()
139 FFDCFile file{FFDCFormat::JSON}; in TEST()
154 FFDCFile file{FFDCFormat::JSON}; in TEST()
173 FFDCFile file{FFDCFormat::JSON}; in TEST()
188 FFDCFile file{FFDCFormat::JSON}; in TEST()
209 FFDCFile file{FFDCFormat::JSON}; in TEST()
/openbmc/openbmc/poky/meta/recipes-devtools/json-c/
H A Djson-c_0.18.bb1 SUMMARY = "A JSON implementation in C"
2 DESCRIPTION = "JSON-C implements a reference counting object model that allows \
3 you to easily construct JSON objects in C, output them as JSON formatted strings \
4 and parse JSON formatted strings back into the C representation of JSON objects."
/openbmc/openbmc/poky/meta/recipes-gnome/json-glib/
H A Djson-glib_1.10.6.bb1 SUMMARY = "JSON-GLib implements a full JSON parser using GLib and GObject"
2 DESCRIPTION = "Use JSON-GLib it is possible to parse and generate valid JSON\
3 data structures, using a DOM-like API. JSON-GLib also offers GObject \
5 instances to and from JSON data types."
/openbmc/phosphor-webui/app/configuration/controllers/
H A Dnetwork-controller.js35 $scope.oldInterface = JSON.parse(JSON.stringify($scope.interface));
176 console.log(JSON.stringify(error));
186 console.log(JSON.stringify(error));
196 console.log(JSON.stringify(error));
208 console.log(JSON.stringify(error));
220 console.log(JSON.stringify(error));
231 console.log(JSON.stringify(error));
247 console.log(JSON.stringify(error));
270 console.log(JSON.stringify(error));
275 console.log(JSON.stringify(error));
[all …]
/openbmc/libcper/
H A DREADME.md1 # CPER JSON Representation & Conversion Library
4 described in UEFI Specification Appendix N) in a human-readable JSON format, in
6 standard CPER binary format and the specified structured JSON.
25 CPER-JSON. The first of these is `cper-convert`, which is a command line tool
27 CPER-JSON through the command line. An example usage scenario is below:
45 Finally, a static library containing symbols for converting CPER and CPER-JSON
46 between an intermediate JSON format can be found generated at
56 The specification for this project's CPER-JSON format can be found in
57 `specification/`, defined in both JSON Schema format and also as a LaTeX
65 between a SatMC and OpenBMC board, including a conversion into CPER JSON for
/openbmc/openbmc/meta-arm/ci/
H A Djunit.sh11 JSON=$BUILDDIR/tmp/log/oeqa/testresults.json
13 if test -f $JSON; then
14 resulttool junit $JSON
/openbmc/phosphor-webui/app/overview/controllers/
H A Dsystem-overview-controller.js41 console.log(JSON.stringify(error));
50 console.log(JSON.stringify(error));
62 console.log(JSON.stringify(error));
70 console.log(JSON.stringify(error));
78 console.log(JSON.stringify(error));
86 console.log(JSON.stringify(error));
99 console.log(JSON.stringify(error));
110 console.log(JSON.stringify(error));
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/perl/
H A Dlibjson-perl_4.05000.bb2 DESCRIPTION = "This package contains the JSON.pm module with friends. \
3 The module implements JSON encode/decode."
5 HOMEPAGE = "https://metacpan.org/pod/JSON"
12 SRC_URI = "git://github.com/makamaka/JSON.git;protocol=https;branch=master"
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/json-spirit/
H A Djson-spirit_4.08.bb1 SUMMARY = "A C++ JSON Parser/Generator Implemented with Boost Spirit."
2 DESCRIPTION = "JSON Spirit, a C++ library that reads and writes JSON files or streams. \
4 already using Boost, you can use JSON Spirit without any additional \
/openbmc/phosphor-webui/app/server-control/controllers/
H A Dpower-usage-controller.js28 console.log(JSON.stringify(error));
36 console.log(JSON.stringify(error));
83 console.log(JSON.stringify(error));
93 console.log(JSON.stringify(error));
/openbmc/webui-vue/
H A Dvue.config.js145 __VUE_OPTIONS_API__: JSON.stringify(true),
149 __VUE_PROD_DEVTOOLS__: JSON.stringify(false),
154 __VUE_PROD_HYDRATION_MISMATCH_DETAILS__: JSON.stringify(false),
157 'process.env.STORE_SESSION': JSON.stringify(
160 'process.env.VUE_APP_STORE_SESSION': JSON.stringify(
/openbmc/openbmc-tools/expectedJsonChecker/
H A DREADME.md1 # Expected JSON Checker tool
3 A tool that cross checks an expected set of JSON entries, by a given index, with
4 a given input set of JSON entries. In addition, there's an ability to filter
6 contain JSON entries. This filtering functionality on cross checking expected
9 Expected entries that only want to be found within the input JSON should use a
16 entries within the BMC's enumerated sensor JSON output against an expected set
19 machine's enumerated sensor data and inventory data to separate JSON files, an
21 created for this machine. These JSON files are then fed into this tool to
23 The machine's name was used as the index into the expected JSON to allow the
24 same expected JSON file to be used across multiple machines instead of having
[all …]
/openbmc/phosphor-power/phosphor-power-sequencer/
H A DREADME.md6 the power sequencer device. The application is configured by an optional JSON
11 - [config_files](config_files/) contains JSON configuration files
12 - [docs](docs/) contains documentation on this application and the JSON
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/yajl/
H A Dyajl_1.0.12.bb1 SUMMARY = "Yet Another JSON Library."
3 DESCRIPTION = "YAJL is a small event-driven (SAX-style) JSON parser \
4 written in ANSI C, and a small validating JSON generator."
H A Dyajl_2.1.0.bb1 SUMMARY = "Yet Another JSON Library."
3 DESCRIPTION = "YAJL is a small event-driven (SAX-style) JSON parser \
4 written in ANSI C, and a small validating JSON generator."
/openbmc/openbmc/poky/meta/recipes-devtools/python/
H A Dpython3-jsonschema-specifications_2025.4.1.bb1 SUMMARY = "The JSON Schema meta-schemas and vocabularies, exposed as a Registry"
2 DESCRIPTION = "JSON support files from the JSON Schema Specifications (metaschemas, \
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/jsoncpp/
H A Djsoncpp_1.9.6.bb1 SUMMARY = "JSON C++ lib used to read and write json file."
2 DESCRIPTION = "Jsoncpp is an implementation of a JSON (http://json.org) reader \
3 and writer in C++. JSON (JavaScript Object Notation) is a \
/openbmc/phosphor-webui/app/access-control/controllers/
H A Duser-controller.js82 console.log(JSON.stringify(error));
99 console.log(JSON.stringify(error));
113 console.log(JSON.stringify(error));
130 console.log(JSON.stringify(error));
152 console.log(JSON.stringify(error));
179 console.log(JSON.stringify(error));
216 console.log(JSON.stringify(error));
250 console.log(JSON.stringify(error));
/openbmc/phosphor-power/phosphor-regulators/docs/
H A DREADME.md6 regulators. The application is controlled by a JSON configuration file.
26 The application is driven by a system-specific JSON configuration file. The JSON
29 behavior that was specified in the JSON file.
51 ## JSON configuration file
53 The JSON configuration file defines the following:
/openbmc/phosphor-fan-presence/
H A DREADME.md21 By default, runtime JSON configuration file(s) are used for each application.
22 The use of YAML configuration file(s) has been deprecated in favor of the JSON
24 once all applications completely support getting their configuration from JSON
68 Meson defaults to JSON based runtime configuration, so to select the YAML
74 ### JSON subsection
78 each using JSON.
80 As JSON based runtime configuration is the default option, no extra options are
87 supported using the JSON based configuration are listed below:**
96 - [Sensor Monitoring](#sensor-monitoring) - Only supports JSON
129 #### JSON subsubsection
[all …]
/openbmc/pldm/tools/fw-update/
H A DREADME.md21 metadatafile Path of metadata JSON file
27 - Providing the metadata JSON file is a must
33 ## Metadata JSON file
37 in JSON format. Typically it is not necessary to write this file each time the
39 metadata JSON files can be reused. The key names used in the metadata JSON
50 - whether those fields need to be specified in the JSON, or are generated by the
55 Metadata JSON must have a key called "PackageHeaderInformation", which is of
74 Metadata JSON must have a key called "FirmwareDeviceIdentificationArea", which
94 - RecordDescriptors: Metadata JSON must have a key called "Descriptors", which
127 Metadata JSON must have a key called "ComponentImageInformationArea", which is

12345678910>>...12