-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
Make Dimension.label source of truth for Dimension identity #6262
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6262 +/- ##
==========================================
+ Coverage 88.47% 88.52% +0.04%
==========================================
Files 323 323
Lines 67647 67906 +259
==========================================
+ Hits 59853 60116 +263
+ Misses 7794 7790 -4 ☔ View full report in Codecov by Sentry. |
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.
My rough understanding is that dim.name
will be used for data access, e.g., looking up a column in a DataFrame and dim.label
will be used by HoloViews for ranges etc. Is this an ok (rough) understanding?
How thoroughly have you checked the codebase for this find and replace? The code still seems to use name
for range lookup.
holoviews/holoviews/plotting/util.py
Line 411 in c8e7f5f
drange = ranges[dimension.name]['data'] |
return {d.name: element.range(d.name, self.data_range) |
Have you checked if hvplot
/ GeoViews
need updating too?
Yes.
Clearly not quite thoroughly enough, will do another more exhaustive check now.
Yes. |
Did miss quite a few. Will scan more thoroughly one more time. Note that this only affects plotting code, so e.g. this isn't affected:
|
Okay, quite confident now, thoroughly reviewed the plotting code and replaced all remaining cases. |
I think the only way we'll catch any more cases will be if we merge and include the change in the RC release. |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Implements #6260