What's important and what can be ignored, should be determined by the backend. The current metadata field priority is not sufficient, though. Looks like we need another field.
It would also be nice to give some hinting as to the width of the column. Probably w/ some kind of data type.
{ type: 'ip' } or { type: 'ips' } or { type: 'timestamp' }
We know max size of ip is 255.255.255.255 and could come up w/ some mapping on the fe to handle this max-px-width.
We could actually implement this now relying on labels though that feels a little naughty. But I don't think we've change the labels thus far..
It would also be nice to give some hinting as to the width of the column. Probably w/ some kind of data type.
{ type: 'ip' }
or{ type: 'ips' }
or{ type: 'timestamp' }
We know max size of ip is
255.255.255.255
and could come up w/ some mapping on the fe to handle this max-px-width.We could actually implement this now relying on labels though that feels a little naughty. But I don't think we've change the labels thus far..