-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Updated Selector to be a user friendly ObjectSelector #316
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I think it should be merged like this,, but in future we should consider flipping it around so that the bulk of the implementation is in Selector, not ObjectSelector, so that we could more clearly steer people to Selector and perhaps eventually deprecate ObjectSelector. But that's complicated by the classes that inherit from ObjectSelector, which would have to call super() in a different way due to the different constructor. So for the foreseeable future, we should probably just make sure our examples use Selector rather than ObjectSelector and leave it at that.
Note: The tests are currently failing due to issues submitting coverage reports to coveralls which is unrelated to this PR. |
Co-Authored-By: jlstevens <[email protected]>
This is nice and convenient in most cases with a shorter name. Addresses the second item listed in holoviz/datashader#698.