[Table Visualization]restore export csv feature to table vis

[ananzh]

Description

• add addtional action in toolbar to allow export data to csv. there are two types of csv, raw and formatted. raw is the original data and formatted is to show formatted Date and percentage data when needed.
• when table is not saved, export csv file will be named as unsaved-raw.csv if choose raw. when table is saved with a filename, it will be saved as [filename]-[raw/formatted].csv

Partically resolved:

#2379

Previous table export feature is build in agg_table.js and agg_table.html :

With DataGrid component, we could use its toolbar. Toolbar is on top of the table vis. We could put export left or right of the toolbar. See what is shown in the example:

We could also add a toolbar option, so toolbar, by default, is not shown when click table vis. When customer needs to export, he/she can click Options button on the right and then add toolbar. Need some UX decisions here.

Currently, table vis with export looks like this:

[manasvinibs]

Is visualization title always present or do we need some default title set?

[ananzh]

good question. Here table vis is using Visualization plugin. title is initiated here

public title: string = '';

when table vis is saved, title will be the saved title. otherwise, it will be an empty string.

[ananzh]

The only place requires initialization is buckets: schemas.bucket || []. This is because for table vis, we defined buckets as a required field in TableVisConfig:

export interface TableVisConfig extends TableVisParams {
  title: string;
  metrics: SchemaConfig[];
  buckets: SchemaConfig[];
  splitRow?: SchemaConfig[];
  splitColumn?: SchemaConfig[];
}

But in Visualization plugin, bucket is defined as any[] || undefined since it is optional, in Schema. Therefore, we need to initiated to [].

export interface Schemas {
  metric: SchemaConfig[];
  bucket?: any[];
  geo_centroid?: any[];
  group?: any[];
  params?: any[];
  radius?: any[];
  segment?: any[];
  split_column?: any[];
  split_row?: any[];
  width?: any[];
  // catch all for schema name
  [key: string]: any[] | undefined;
}

[manasvinibs]

SchemaConfig

I see! Is there a specific reason as to why buckets is a required field in Table vis?

[manasvinibs]

@ananzh Just curious to know why CI checks have been omitted on this PR? Is it because this is going into feature branch? Also, is the change going to get into main incrementally or will it has to be done with other changes for table visualization? Is this change planned for next major release?

[ananzh]

Yes, you are right. It is due to feature branch. Once we put everything together and send table vis to main, then it will run through all the tests.