fix issue where passing None as parameter to a query would fail #8
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.
Motivation
It was pointed out by the platform team, specifically @Pive01 (thank you! 🙏), that #6 introduced a bug, where you could no longer pass
Noneas a parameter value. This created a failure downstream. For example, this is a reasonable way to create a param dict:This PR adds tests, updates the type hints, and fixes the underlying error. Also bumps the version to 0.5.2
Changes
Nonevalues can now be passed as parameters again to thequeryandpipesapi.