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/events/event_state_sensor.json b/libpldmresponder/examples/events/event_state_sensor.json
index 6ab566e..17ce751 100644
--- a/libpldmresponder/examples/events/event_state_sensor.json
+++ b/libpldmresponder/examples/events/event_state_sensor.json
@@ -1,8 +1,8 @@
-# Each entry is to uniquely identify a remote state sensor(there are separate
-# entry for each sensor in a composite sensor) and the supported event states.
-# The "dbus" section contains information about the corresponding D-Bus
-# property for the sensor and "property_values" are the D-Bus property values
-# for each corresponding entry in the "event_states"
+// Each entry is to uniquely identify a remote state sensor(there are separate
+// entry for each sensor in a composite sensor) and the supported event states.
+// The "dbus" section contains information about the corresponding D-Bus
+// property for the sensor and "property_values" are the D-Bus property values
+// for each corresponding entry in the "event_states"
{
"entries": [
{