Fix tree.find_by_path([])
#288
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
I expect this should return `nil` I've also added a number of similar specs of passing all the blank values I can think of as find_by_tree didn't seem to already be tested with these various blank values.
|
There seems to be something wrong with travis |
|
Thanks! Your diff lgtm. I restarted travis. |
|
is there anything more you need from me before merging this? |
|
Nope, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously
Tag.find_by_tree([])would return essentiallyTag.first.This was confusing as I expected it this should return
nil.I've also added a number of similar specs of passing all the blank values I can think of
as
Tag.find_by_treedidn't seem to already be tested with these various blank values.