[DO NOT MERGE] Possible implementation of map types example

capabilities/doors.yml

@@ -55,10 +55,24 @@ properties:
     name: locks
     name_cased: locks
     name_pretty: Locks
+    # Type for the value. In L14 all map types will lose the key from the object.
+    # Also in L14, this would denote the type of the map VALUES
     type: types.lock
+    # This would become false in L14, unless the values inside the map are multiple
     multiple: true
     name_singular: lock
     description: Lock states for the given doors
+    # Denotes a map type. Safely ignored in L13
+    map: true
+    # The name we use for the key.
+    # In L13, this denotes the key to be considered exlusive in the value object
+    # In L14, maybe we need that somewhere. or we'll just ignore it ¯\_(ツ)_/¯
+    key_name: location
+    # Which values the map key has. For L14 use only.
+    # This could be either a pointer to a type in custom_type, 
+    # or maybe we could put these in another file? Like map_keys.yaml,
+    # and then this would be keys.location
+    key_type: types.location # or keys.location
     examples:
       - data_component: '0000'
         values:

misc/key_types.yml

@@ -0,0 +1,23 @@
+#
+# key_types.yml
+#
+#
+# Defines the key types used in AutoAPI.
+# 
+# Referred to as 'keys.<name>'
+
+keys:
+  - name: location
+    name_cased: location
+    name_pretty: Location
+    type: enum
+    size: 1
+    enum_values:
+      - id: 0x00
+        name: front_left
+      - id: 0x01
+        name: front_right
+      - id: 0x02
+        name: rear_right
+      - id: 0x03
+        name: rear_left