Open
Conversation
when user provides a arg in lq [query_name] [args] prev behavior is to treat args as strings now it attempts to convert to int when possible(and leaves it as it is when failed)
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 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.
when user provides a arg in
lq [query_name] [args]
prev behavior is to treat args as strings
now it attempts to convert to int when possible(and leaves it as it is when failed)
the change is useful when you want to have db-id as args
for example ,
for this query i run run
lq block-content 1577previously it finds nothing because it treats 1577 as "1577"
not it finds the content because it treats 1577 properly as db/id