[BUG] Using array/list in line_dash for hspan doesn't work about bokeh

[mattpap]

plot.hspan(y=0, line_dash=[5, 5])

line_dash=[5, 5] is interpreted in this context as two data points with line_dash=5, which on its own doesn't make sense and lack of proper validation of scalar/vector properties allows this to be propagated to bokehjs. The best way to deal with array scalars is to use the following syntax:

from bokeh.core.properties import value
plot.hspan(y=0, line_dash=value([5, 5]))

This way no interpretation will be performed and the resulting plot will work as expected.

[bryevdv]

Is this something specific to hspan? Or a new development? I am nearly 100% certain that line_dash=[5, 5] has worked in other contexts in the past.

[huaracheguarache]

line_dash=[5, 5] works with line, which is why I found it curious that it didn't work with hspan. It also doesn't work with vspan when I checked just now. @mattpap's suggested workaround fixes the issue for hspan and vspan.

[mattpap]

line_dash=[5, 5] works with line

This works, because Line glyph uses scalar visual properties, i.e. you provide a single value for all data points, thus an array is interpreted as a value. HSpan and VSpan glyphs, however, use vectorized visual properties and thus the interpretation is different.

[mattpap]

Is this something specific to hspan? Or a new development? I am nearly 100% certain that line_dash=[5, 5] has worked in other contexts in the past.

It always worked like this. Another similar prominent case is Figure.image_rgba(image=[img]) (or image=value(img)). As mentioned in my previous comment, the difference for line_dash comes from the difference in behavior between scalar and vector visual properties.

[mattpap]

Alternatively one can also use this:

plot.hspan(y=0, line_dash=[[5, 5]])

[bryevdv]

I think this can be made to meet expectations, so I would suggest we triage as a bug. For specialized line-dash properties I think it would acceptable for a vector spec to inspect the entire given value to see whether it is a flat list, or a nested list, and act accordingly.

Edit: IIRC the original concern with image glyphs was the cost of inspecting potentially large data structures in the ragged array case, but now that we no longer accept ragged arrays as input maybe the image case could be similarly improved (but that deserves a separate issue)