Fix json files
I accidentally tested pldm with a json linter and found a lot
of json issues in pldm, this commit would try to fix all of them.
The issues that are fixed in this commit are
1. As per nlohmann json, it only support // & /**/ for comments
and those can be treated as spaces when we pass "true" for the
skipcomments argument for the json::parse() function. Most of
the places we used # for commenting.
2. RFC 7159 does not support hexadecimal numbers in json,so replacing
it with its decimal equivalent.
3. This commit also adds the configuration files for eslint json linting
as well the eslintignore configuration.
Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I909fae9ded93f47273276593fdf758449252f52f
diff --git a/libpldmresponder/examples/fru/Board_VINI.json b/libpldmresponder/examples/fru/Board_VINI.json
index fd58717..fbb710a 100644
--- a/libpldmresponder/examples/fru/Board_VINI.json
+++ b/libpldmresponder/examples/fru/Board_VINI.json
@@ -1,19 +1,19 @@
-# This JSON has the information needed to create OEM FRU record VINI for FRU of
-# type Board.
+// This JSON has the information needed to create OEM FRU record VINI for FRU of
+// type Board.
{
"record_details":
{
- # FRU Record Type - OEM FRU Record
+ // FRU Record Type - OEM FRU Record
"fru_record_type" : 254,
- # Encoding Type for FRU fields - ASCII
+ // Encoding Type for FRU fields - ASCII
"fru_encoding_type": 1,
"dbus_interface_name": "xyz.openbmc_project.Inventory.Item.Board"
},
"fru_fields":[
{
- # FRU Field Type 2 - Keyword RT
+ // FRU Field Type 2 - Keyword RT
"fru_field_type" : 2,
- # D-Bus property to read and populate the FRU field
+ // D-Bus property to read and populate the FRU field
"dbus":
{
"interface" : "com.ibm.ipzvpd.VINI",
@@ -22,9 +22,9 @@
}
},
{
- # FRU Field Type 3 - Keyword B3
+ // FRU Field Type 3 - Keyword B3
"fru_field_type" : 3,
- # D-Bus property to read and populate the FRU field
+ // D-Bus property to read and populate the FRU field
"dbus":
{
"interface" : "com.ibm.ipzvpd.VINI",