labelfont, tickfont and rangefont string property

[dy]

Now to set custom font for an axis we have to pass an object to labelfont property:

Plotly.plot(document.body, {
  data: {
    ...
    labelfont: {family: 'Roboto, sans-serif'}
    ...
  }
})

What if instead we could just use string:

Plotly.plot(document.body, {
  data: {
    ...
    labelfont: 'Roboto'
    ...
  }
})

Plain css font string would be so intuitive!

Also I would suggest introducing an alias for labelFont - that is easy to miss a letter.

[dy]

Ok, seems to be problematic with existing coerceFont implementation, since we can't check which type of value passed.

[etpinard]

Also I would suggest introducing an alias for labelFont - that is easy to miss a letter.

That's not going to happen, all plotly.js "data" and "layout" attributes are written in smashedtogether case with a few exceptions like error_y and error_x.

[etpinard]

@dfcreative that's an interesting idea and I don't think it would be that hard to implement.

We could just add check for isPlainObject(attr) here in coerceFont and split family, size and color using a regex.

Now, down the road, we're planning on adding optional outline colors for fonts (see #1597) which wouldn't fit within the css font realm. So, I'm having doubts adding another attribute-value pathway.

[etpinard]

This one most likely won't happen. Closing.