Fix YAML formatting with prettier hook

Author: alexdewar

schemas/input/agent_commodity_portions.yaml

@@ -20,7 +20,8 @@ fields:
   - name: years
     type: string
     description: The year(s) to which this entry applies
-    notes: One or more milestone years separated by semicolons, `all` to select all years or a year
+    notes:
+      One or more milestone years separated by semicolons, `all` to select all years or a year
       range in the form 'start..end' to select all valid years within range, inclusive. Either 'start'
       'end' or both can be omitted, which will set the corresponding limit to the minimum or maximum
       valid year, respectively.

schemas/input/agent_objectives.yaml

@@ -16,7 +16,8 @@ fields:
   - name: years
     type: string
     description: The year(s) to which this entry applies
-    notes: One or more milestone years separated by semicolons, `all` to select all years or a year
+    notes:
+      One or more milestone years separated by semicolons, `all` to select all years or a year
       range in the form 'start..end' to select all valid years within range, inclusive. Either 'start'
       'end' or both can be omitted, which will set the corresponding limit to the minimum or maximum
       valid year, respectively.

schemas/input/agent_search_space.yaml

@@ -16,7 +16,8 @@ fields:
   - name: years
     type: string
     description: The year(s) to which this entry applies
-    notes: One or more milestone years separated by semicolons, `all` to select all years or a year
+    notes:
+      One or more milestone years separated by semicolons, `all` to select all years or a year
       range in the form 'start..end' to select all valid years within range, inclusive. Either 'start'
       'end' or both can be omitted, which will set the corresponding limit to the minimum or maximum
       valid year, respectively.

schemas/input/commodity_levies.yaml

@@ -20,7 +20,8 @@ fields:
   - name: years
     type: string
     description: The year(s) to which this entry applies
-    notes: One or more milestone years separated by semicolons, `all` to select all years or a year
+    notes:
+      One or more milestone years separated by semicolons, `all` to select all years or a year
       range in the form 'start..end' to select all valid years within range, inclusive. Either 'start'
       'end' or both can be omitted, which will set the corresponding limit to the minimum or maximum
       valid year, respectively.

schemas/input/demand.yaml

@@ -17,7 +17,8 @@ fields:
   - name: year
     type: string
     description: The year(s) to which this entry applies
-    notes: One or more milestone years separated by semicolons, `all` to select all years or a year
+    notes:
+      One or more milestone years separated by semicolons, `all` to select all years or a year
       range in the form 'start..end' to select all valid years within range, inclusive. Either 'start'
       'end' or both can be omitted, which will set the corresponding limit to the minimum or maximum
       valid year, respectively.

schemas/input/process_availabilities.yaml

@@ -22,7 +22,8 @@ fields:
   - name: years
     type: string
     description: The milestone year(s) to which this entry applies
-    notes: One or more milestone years separated by semicolons, `all` to select all years or a year
+    notes:
+      One or more milestone years separated by semicolons, `all` to select all years or a year
       range in the form 'start..end' to select all valid years within range, inclusive. Either 'start'
       'end' or both can be omitted, which will set the corresponding limit to the minimum or maximum
       valid year, respectively.

schemas/input/process_flows.yaml

@@ -23,7 +23,8 @@ fields:
   - name: years
     type: string
     description: The year(s) to which this entry applies
-    notes: One or more milestone years separated by semicolons, `all` to select all years or a year
+    notes:
+      One or more milestone years separated by semicolons, `all` to select all years or a year
       range in the form 'start..end' to select all valid years within range, inclusive. Either 'start'
       'end' or both can be omitted, which will set the corresponding limit to the minimum or maximum
       valid year, respectively.

schemas/input/process_parameters.yaml

@@ -19,7 +19,8 @@ fields:
   - name: years
     type: string
     description: The milestone year(s) to which this entry applies
-    notes: One or more milestone years separated by semicolons, `all` to select all years or a year
+    notes:
+      One or more milestone years separated by semicolons, `all` to select all years or a year
       range in the form 'start..end' to select all valid years within range, inclusive. Either 'start'
       'end' or both can be omitted, which will set the corresponding limit to the minimum or maximum
       valid year, respectively.

schemas/input/processes.yaml

@@ -28,14 +28,17 @@ fields:
     notes: Must be >= to `start_year`
   - name: capacity_to_activity
     type: number
-    description: Factor relating capacity units (e.g. GW) to activity units (e.g. PJ). It is the
+    description:
+      Factor relating capacity units (e.g. GW) to activity units (e.g. PJ). It is the
       maximum activity per year for one unit of capacity.
     notes: Must be >=0. Optional (defaults to 1.0).
   - name: unit_size
     type: number
-    description: Capacity of the units in which an asset for this process will be divided into when
+    description:
+      Capacity of the units in which an asset for this process will be divided into when
       commissioned, if any.
-    notes: If present, must be >0. Optional (defaults to None). Assets with a defined unit size are
+    notes:
+      If present, must be >0. Optional (defaults to None). Assets with a defined unit size are
       divided into n = ceil(C / U) equal units, where C is overall capacity and U is unit_size
       (i.e. rounding up the number of units, which may result in a total capacity greater than C, if
       C is not an exact multiple of U).