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/FRU_Master.json b/libpldmresponder/examples/fru/FRU_Master.json
index 73c7ebb..710c5e1 100644
--- a/libpldmresponder/examples/fru/FRU_Master.json
+++ b/libpldmresponder/examples/fru/FRU_Master.json
@@ -1,16 +1,16 @@
-# This is the master config file for generating PLDM FRU records from the D-Bus
-# inventory objects. "service" is the name of D-Bus service hosting the
-# inventory D-Bus objects, "root_path" is the root path for all the inventory
-# D-Bus objects and "entities" section specifies the type of FRU's for which
-# FRU records are created in the FRU table. FRU Record Set PDR and Entity
-# Association PDR are generated for matching FRU. In this example, PLDM FRU
-# records will be created for all FRU's of type Board and CPU. The "entity_type"
-# field is the PLDM entity type for Board and CPU. For each FRU type,
-# corresponding config JSON's are needed for each record. In the example
-# directory, Board_General.json is the config to generate the General FRU
-# record for FRU of type Board and Board_VINI.json is the config to generate
-# the OEM record (VINI is a record in IBM IPZ VPD format) for FRU of type Board.
-# For all instances of the same FRU, the same config JSON will apply.
+// This is the master config file for generating PLDM FRU records from the D-Bus
+// inventory objects. "service" is the name of D-Bus service hosting the
+// inventory D-Bus objects, "root_path" is the root path for all the inventory
+// D-Bus objects and "entities" section specifies the type of FRU's for which
+// FRU records are created in the FRU table. FRU Record Set PDR and Entity
+// Association PDR are generated for matching FRU. In this example, PLDM FRU
+// records will be created for all FRU's of type Board and CPU. The "entity_type"
+// field is the PLDM entity type for Board and CPU. For each FRU type,
+// corresponding config JSON's are needed for each record. In the example
+// directory, Board_General.json is the config to generate the General FRU
+// record for FRU of type Board and Board_VINI.json is the config to generate
+// the OEM record (VINI is a record in IBM IPZ VPD format) for FRU of type Board.
+// For all instances of the same FRU, the same config JSON will apply.
{
"service":"xyz.openbmc_project.Inventory.Manager",
"root_path":"/xyz/openbmc_project/inventory",