Chronograf: As a backend I can save y ranges on a cell

[121watts]

For a given cell on a dashboard we need another field on the cell object to persist range selection. Something like:

{
  x: 0,
  y: 0,
  ...
  ranges: {
    y: [0, 1],
    y2: [null,  null],
  },
}

Open to a different shape for ranges. Something like

ranges: [
    {
      axis: 'y',  
      bounds: [0, 1]
    },
    {
      axis: 'y2',  
      bounds: [0, 1]
    },
  ]

[jaredscheib]

lol @ title

[timraymond]

I would like @goller 's input on this before this is taken on. After spending some time reviewing the existing API, I think this would require a data migration as an equivalent API already exists here:

The current API is inconvenient from the way #1714 is put together. However, the proposed API destroys context provided by having view information like ranges and labels associated with queries, which may be beneficial to some clients.

[121watts]

We can talk more about this when you're back.

[nhaugo]

@timraymond i don't think I understand. If this is an optional field there is no migration step that would be needed. What makes adding this field inconvenient.

This has nothing do do with the query, it is part of the visual representation. It belongs on the cell object.

[121watts]

@goller i think we settled on something like this added to the cell:

{
  axes: {
     y: {min: 0, max: 1},
     y2: {..., label: "foo"}
  },
}

[goller]

{
    "axes": {
        "y": {
            "bounds": [
                0,
                1
            ]
        },
        "y2": {
            "bounds": [
                0,
                1
            ]
        },
        "x": {
            "bounds": []
        }
    }
}