-
-
Notifications
You must be signed in to change notification settings - Fork 32
Conversation
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.
Given linting shenanigans, we should probably merge #96 first.
The caveat looks good though!
e0f1963
to
d0f8352
Compare
d0f8352
to
f36220a
Compare
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.
I want to suggest we make the name more specific by changing it to limitResponseLength
, but then this is good to go!
@rekmarks - done |
p.s Github might not be showing there's another commit, but there is. 👀 |
3a53f66
to
4decc55
Compare
Fixed with a rebase, change is now actually there |
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.
LGTM!
I think we need to introduce more extensive caveat validation (ala PropTypes
, because do we really want a limitResponseLength
value of 0
or -1
?), but that'll be its own PR.
Adds a limitResponse caveat that slices an array response to the specified length.