You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: policy/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -334,7 +334,7 @@ An individual `Rule` object is defined by the following fields:
334
334
|`geography_id`| UUID | Required | Unique ID of [Geography](/geography#general-information)|
335
335
| `geography_json` | JSON | Required | The GeoJSON that defines the geographical coordinates.
336
336
| `effective_date` | [timestamp][ts] | Optional | `start_date` for first published policy that uses this geo. Server should set this when policies are published. This may be used on the client to distinguish between “logical” geographies that have the same name. E.g. if a policy publishes a geography on 5/1/2020, and then another policy is published which references that same geography is published on 4/1/2020, the effective_date will be set to 4/1/2020.
337
-
|`publish_date`|[timestamp][ts]| Required | Timestamp that the policy was published, i.e. made immutable |
337
+
|`published_date`|[timestamp][ts]| Required | Timestamp that the policy was published, i.e. made immutable |
338
338
|`prev_geographies`| UUID[]| Optional | Unique IDs of prior [geographies](/geography#general-information) replaced by this one |
0 commit comments