summaryrefslogtreecommitdiffstats
path: root/entity_map_json.cpp
Commit message (Collapse)AuthorAgeFilesLines
* drop entity YAML in favor of json provided filePatrick Venture2019-09-191-12/+2
| | | | | | | | | | Step 5 of moving from entity map from YAML to JSON drops support for a built-in YAML mapping of the entity containers. Tested: Not tested. No platform upstream updates this YAML file in their builds. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ic2918f568f5a6f4a9f9135990889b3bb84a0c81d
* sensorhandler: use entity-map from json if filledPatrick Venture2019-09-191-2/+28
| | | | | | | | | | Step 4 of the transition from YAML to JSON will return the data from the JSON file if present and valid, otherwise it'll fallback and return the default example YAML present in the repository. Tested: This was not tested. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I33c773fc53660a9eb5e27a8c8c3e231c64fe079d
* entitymap: move accessor to separate modulePatrick Venture2019-09-171-0/+7
| | | | | Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I8c80acb694d067043b77d81dbb9a7ba0057fef56
* entitymap: add json file loading if presentPatrick Venture2019-08-231-0/+22
| | | | | | | | | | Step 3 to handle the entity-map transition from YAML to JSON. This patchset adds a method that will process the json file, if present to build the map. Tested: This patchset has not been tested. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I79297aef59844a21f20c0a77de7a21264e2ed96a
* entitymap: add json parsing supportPatrick Venture2019-08-201-0/+74
Add a json parsing method that given an entity map in the format: [ { "id" : 1, "containerEntityId" : 2, "containerEntityInstance" : 3, "isList" : false, "isLinked" : false, "entities" : [ {"id" : 1, "instance" : 2}, {"id" : 1, "instance" : 3}, {"id" : 1, "instance" : 4}, {"id" : 1, "instance" : 5} ] } ] is constructed into the entity map used by sensorhandler. This is meant as part of the transition from the entity map in YAML to JSON. This is step 2. Step 1 moved access to the object behind a method. This adds JSON validation and parsing. Step 3 will add a file path to check and parse. Step 4 will provide a call to parse that file if present and use its data if non-empty. Tested: The method added has not been tested beyond unit-test validation. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ic29f022d3812fa9e3af775d542ad055629fd5a01
OpenPOWER on IntegriCloud