riverbankcms 0.32.1 → 0.32.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -681,6 +681,18 @@ provider evidence, job/storage keys and archive descriptors are never public.
681
681
  }
682
682
  ```
683
683
 
684
+ ### What happens when a venue or category field is missing
685
+
686
+ `riverbankcms push` treats the file as the whole record. If you remove
687
+ `description`, `capacity` or `mapEmbed` from a venue file, or `description` or
688
+ `color` from a category file, the push clears that value on the site. A venue's
689
+ `locationValue` is the exception: if you leave it out the saved location stays,
690
+ so set it to `null` to remove it.
691
+
692
+ Your own scripts work the way the dashboard does. When you call
693
+ `client.venues.upsert()` or `client.eventCategories.upsert()`, any field you
694
+ leave out keeps its saved value, and `null` clears it.
695
+
684
696
  ### Event File Format
685
697
 
686
698
  `content/events/yoga-class.json`: