Don't query default nsites and nelements values #178
Merged
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 work is inspired by issue #125, in the sense that COD was failing to handle
nsites
, and this is added by default even if the user has not changed it. There is no need to add a query for a non-filter. Hence, this PR will make sure to not addnsites
andnelements
to the query filter if they are equal to their initial values.A custom
IntRangeSlider
widget is implemented to handle returning aNone
value.The custom
IntRangeSlider
widget simply implements aget_value()
function that is used instead of getting thevalue
attribute, which. It will return(None, None)
if the values are equal to themin
andmax
attributes, respectively. If only one value is altered the other will beNone
.