Allow any status change to include an associated_trip

PR #297 already updated the spec language to make it clear that any status change is allowed to have an `associated_trip`, but I didn't realize this was incompatible with the existing schema. The schema should now match the spec, which states that `user_pick_up` and `user_drop_off` events must have an `associated_trip` but other events may have one when applicable.
openmobilityfoundation · Oct 1, 2019 · 8e4a297 · 8e4a297
1 parent 3ec99ad
commit 8e4a297
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/provider/dockless/status_changes.json b/provider/dockless/status_changes.json
@@ -375,7 +375,7 @@
               },
               {
                 "description": "conditionally require associated_trip when applicable",
-                "oneOf": [
+                "anyOf": [
                   {
                     "not": {
                       "properties": {

diff --git a/schema/templates/provider/status_changes.json b/schema/templates/provider/status_changes.json
@@ -173,7 +173,7 @@
               },
               {
                 "description": "conditionally require associated_trip when applicable",
-                "oneOf": [
+                "anyOf": [
                   {
                     "not": {
                       "properties": {