-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarifies that expire_time
is not available for endpoint exceptions
#3856
Conversation
Documentation previews: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some minor suggestions, but overall LGTM! Thank you!
@@ -43,7 +43,7 @@ A JSON object with these fields: | |||
exception queries. Boolean `AND` logic is used to evaluate the relationship | |||
between array elements. If you want to use `OR` logic, create a separate | |||
exception item. |Yes | |||
|`expire_time` |String |An expiration date in ISO format. |No | |||
|`expire_time` |String |An expiration date in ISO format. This field is not available for endpoint exceptions. |No |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Users can likely infer that this param only works for regular exceptions, but it might be better to directly state that and remove any potential for ambiguity.
|`expire_time` |String |An expiration date in ISO format. This field is not available for endpoint exceptions. |No | |
|`expire_time` |String a|Specify when an exception item expires. The expiration date must be in ISO format. | |
NOTE: This field is only available for regular exception items, not endpoint exceptions. |No |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @nastasha-solomon! I agree it's better to be explicit in this case – I'll make that change.
For the sake of consistency, I'd slightly tweak your suggestion for the first sentence, since most of the other parameter descriptions start with a noun phrase rather than an imperative verb. How does this sound:
The exception item's expiration date, in ISO format. This field is only available for regular exception items, not endpoint exceptions.
@@ -26,7 +26,7 @@ When unspecified, a new comment is created. | |||
exception queries. Boolean `AND` logic is used to evaluate the relationship | |||
between array elements. If you want to use `OR` logic, create a separate | |||
exception item. |Yes | |||
|`expire_time` |String |An expiration date in ISO format. |No | |||
|`expire_time` |String |An expiration date in ISO format. This field is not available for endpoint exceptions. |No |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as above if you decide to accept it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM and I like your proposed edit based on Nastasha's comment, @natasha-moore-elastic
Previews: