Allows history to enforce to return minimum number of events for a given type - #56
Merged
Merged
Conversation
Member
Author
|
Committed for now. I've tested it and so far worked as expected. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allow the user to call
history()to select a specific number of events of a given kind.Fixes: #45
@asantaga I had to add the new parameter
enforce_limitto don't the current API. So this way, the old behavior continues the same, however it can be enforced now with the new parameters.Please give a try or let me know if that looks for your so then we can commit and publish the newer version since this is the last issue for the
0.1.5milestone.Thank you!