Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleaned up Element range handling #1876

Merged
merged 1 commit into from
Sep 13, 2017
Merged

Cleaned up Element range handling #1876

merged 1 commit into from
Sep 13, 2017

Conversation

philippjfr
Copy link
Member

As described in #1870, QuadMesh is currently not handling explicitly set dimension ranges. This PR adds a utility to combine the data range with the dimension ranges and uses it in various Element.range implementations.

@philippjfr philippjfr added type: bug Something isn't correct or isn't working tag: component: data labels Sep 12, 2017
@philippjfr philippjfr force-pushed the quadmesh_range branch 2 times, most recently from 643fa8f to 5c493a4 Compare September 12, 2017 14:29
"""
Computes the range along a dimension by combining the data range
with the Dimension soft_range and range.
"""
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would be surprised if we don't have very similar logic to this somewhere else in holoviews already...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see you replaced two chunks of code with this utility below, is that everywhere this utility could be used?

@jlstevens
Copy link
Contributor

Looks good.

It would be good if you could check that dimension_range can't be used in more places (I suspect so, but I might be wrong!). Otherwise happy to merge.

@philippjfr philippjfr force-pushed the quadmesh_range branch 2 times, most recently from 35e02c3 to 6a0ab9b Compare September 12, 2017 22:06
@philippjfr philippjfr changed the title Cleaned up Element range handling and fixed QuadMesh range Cleaned up Element range handling Sep 12, 2017
@philippjfr
Copy link
Member Author

I think this was long overdue tbh, there were various inconsistencies in the implementations.

@philippjfr philippjfr force-pushed the quadmesh_range branch 4 times, most recently from 09a5fb1 to 0c76497 Compare September 12, 2017 23:47
@jlstevens
Copy link
Contributor

Tests are green, if you think you've used this new utility everywhere that makes sense, I'm happy to merge.

@philippjfr
Copy link
Member Author

Yes, that's every single range implementation now.

@jlstevens jlstevens merged commit 204941a into master Sep 13, 2017
@philippjfr philippjfr deleted the quadmesh_range branch September 28, 2017 20:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tag: component: data type: bug Something isn't correct or isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants