Create new named color scales in config section

Is it possible to add new named color scales in config section? Like this example:

"config":{
  . . .
    "newColorScaleName":["#800000","#FF0000","#FFA07A"]
  . . .
}

[jheer]

I believe the issue is that here the spec is defining new named scale ranges and then trying to look them up dynamically. However, named ranges like "category10" are added to the specification at parse time, and so can not be accessed at runtime using signals.

While schemes can be dynamically added (via the Vega API) we do not currently support defining new scheme entries directly in the config. In general this would be difficult to do, as schemes are not defined per-view but rather for the entire Vega library. So if multiple specifications were used on the same page, they might conflict in their use of schemes. We’d have to invent a tiered approach that allowed schemes to be name-spaced within a View only.

As a way of avoiding all of this, I would recommend defining your custom color palettes in an individual signal instead, and then looking them up by key to provide dynamic scale ranges. Here’s an example.

[domoritz]

As far as I understand the issue is that

  "config":{
    "range": {
      "mycolors": ["red", "yellow", "blue"]
    }
  },

does not create a new color scale but instead sets the default range. I marked this issue as a feature request since I don’t know whether we support what you are asking for right now.