This repository was archived by the owner on Mar 17, 2021. It is now read-only.
fix: limit should always be a number and 0 value handles as number#180
Merged
alexander-akait merged 1 commit intomasterfrom Jun 5, 2019
Merged
Conversation
BREAKING CHANGE: `limit` should always be a number and 0 value handles as number
|
@evilebottnawi So setting 0 as the limit does what? Is the behaviour the same as undefined in 1.x.x, or does it essentially prevent the plugin from working? This would be good to add in the docs or release notes. |
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.
2 participants
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.
This PR contains a:
Motivation / Use-Case
Description
Breaking Changes
BREAKING CHANGE:
limitshould always be a number and 0 value handles as numberAdditional Info
No