Fix Drop#key? so it can handle a nil argument #6281
Merged
Conversation
This file contains 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
Crunch09
approved these changes
Aug 8, 2017
ghost
approved these changes
Aug 8, 2017
|
@jekyllbot: merge +fix |
jekyllbot
added a commit
that referenced
this pull request
Aug 9, 2017
parkr
added a commit
that referenced
this pull request
Aug 10, 2017
parkr
added a commit
that referenced
this pull request
Aug 10, 2017
Backport #6281 for v3.5.x: Fix Drop#key? so it can handle a nil argument
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.
In Liquid 4.0,
Liquid::VariableLookup#evaulatechecksinput.key?when it's evaluating. If thekeyisnil, it throws the following error:We should simply return
falseforDrop#key?(nil)./cc @jekyll/stability