You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a number of keywords that accept a set of values (usually strings). In HoloViews, they are usually declared in a Selector Parameter, so they are more organized and more exposed than in hvPlot which doesn't use Param.
Here's a non-exhaustive list:
Customization:
xaxis/yaxis: e.g. top, bottom, right, left
legend: top, bottom, right, left
tools: e.g. tap, box_select
hover: vline, hline
widget_location
Downsampling:
aggregator: e.g. mean, count, min, max,
downsample: e.g. lttb, minmax, m4
Geographic:
coastline: e.g. 10m, 50m
features: e.g. borders, lakes
I would like to discuss whether having them available as Enums in hvPlot would help improve the user experience. As suggested by @ahuang11, if we were to rely on Enums they should probably be first added to HoloViews. Here's the sort of change we could make in HoloViews, adding an Enum for legend_position and updating the Parameter in a way that doesn't change it at all.
This discussion was converted from issue #1498 on May 23, 2025 06:57.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
There are a number of keywords that accept a set of values (usually strings). In HoloViews, they are usually declared in a
Selector
Parameter, so they are more organized and more exposed than in hvPlot which doesn't use Param.Here's a non-exhaustive list:
Customization:
Downsampling:
Geographic:
I would like to discuss whether having them available as Enums in hvPlot would help improve the user experience. As suggested by @ahuang11, if we were to rely on Enums they should probably be first added to HoloViews. Here's the sort of change we could make in HoloViews, adding an Enum for
legend_position
and updating the Parameter in a way that doesn't change it at all.hvPlot could expose the Enums in its top-level module.
So users can leverage them easily:
Beta Was this translation helpful? Give feedback.
All reactions