JSON Mock with numeric Funnel.line.dash value

I have the mock funnel_vertical_overlay_custom_arrays.json that sets the line dash to 10. Would I be correct in assuming that a value of "10" is ok (i.e: changing the mock value to string is correct)? For the values 0 to 5 I assume 0 refers to "solid", no? If so I guess the value 10 is incorrect?

Looking at the schema below it seems like this is a candidate for “enumerate”. This would allow the Scala API to set the correct value. I see that issue https://github.com/plotly/plotly.js/issues/2903 has already referred to this possibility. Would it make sense for me to make a request?

TIA.

                "connector": {
                    "line": {
                        "color": {
                            "valType": "color",
                            "role": "style",
                            "editType": "style",
                            "description": "Sets the line color.",
                            "dflt": "#444"
                        },
                        "width": {
                            "valType": "number",
                            "min": 0,
                            "dflt": 2,
                            "role": "style",
                            "editType": "plot",
                            "description": "Sets the line width (in px)."
                        },
                        "dash": {
                            "valType": "string",
                            "values": [
                                "solid",
                                "dot",
                                "dash",
                                "longdash",
                                "dashdot",
                                "longdashdot"
                            ],
                            "dflt": "solid",
                            "role": "style",
                            "editType": "style",
                            "description": "Sets the dash style of lines. Set to a dash type string (*solid*, *dot*, *dash*, *longdash*, *dashdot*, or *longdashdot*) or a dash length list in px (eg *5px,10px,2px,2px*)."
                        },
                        "editType": "plot",
                        "role": "object"
                    },

[alexcjohnson]

Also that mock has marker.line.dash which is not supported, we should remove that from the mock. So this is just about connector.line.dash.

The key part of the attribute description is “or a dash length list in px (eg *5px,10px,2px,2px*)” - That’s a freeform string - following a pattern, but not enumerable. But we list values in the schema because these are special values that are interpreted dynamically. Aside from solid, these do not have a fixed representation as dash length lists, as we scale the dash lengths with line width.

Side note: according to the docs you actually should not use “px” in the attribute as we suggest in the description, though AFAIK browsers universally accept it that way.

10 is coerced to "10" and then interpreted by stroke-dasharray as “10px on, 10px off.” 0 ends up solid, but only because the browser doesn’t know what to do with “0px on, 0px off”, not because we assign values to the special strings.

[hmf]

My JS knowledge is next to 0 and getting to know Plotly.js code is not doable. I have already bitten off more than I can chew on this Scala wrapper thingy. Went down this rabbit hole thinking I would have it done in a couple of weeks. 8-( I will change the mock to string and hold off on the validation. Thanks for everyone’s help.