plugins, discussion: Revise on dataProcess & dataAccess

[WenheLI]

While developing plugins, I found that the functionalities of dataProcess & dataAccess have some overlaps since they both functioned for data manipulation with different scopes (dataProcess for one sample & dataAccess for the whole dataset).

Discussed with @yorkie, we think it would be more intuitive to move all data manipulation logics to dataProcess. (This requires us to introduce two types of dataProcess -- one for global; one for local).

Any ideas/suggestions on the current revise?

[yorkie]

@WenheLI Is there a way to be compatible with DataProcessType in which 1st argument is a Sample?

[WenheLI]

interface DataProcessType extends PipcookPlugin {
  (data: Sample | UniDataset, metadata: Metadata, args: ArgsType): Promise<void>;
}

or

interface IDataProcess {
    sample?: Sample,
    dataset?: UniDataset
}

interface DataProcessType extends PipcookPlugin {
  (data: IDataProcess, metadata: Metadata, args: ArgsType): Promise<void>;
}

Two implementations that come into my mind. : ( Though I do not think they are in good shape.
IMO, two separate sub-types would be better:

interface DataProcessType extends PipcookPlugin {
  (data: Sample, metadata: Metadata, args: ArgsType): Promise<void>;
}

interface GlobalDataProcessType extends PipcookPlugin {
  (data: UniDataset, metadata: Metadata, args: ArgsType): Promise<void>;
}

[yorkie]

How about this?

interface CommonDataProcessType extends PipcookPlugin {
  (data: Sample, metadata: Metadata, args: ArgsType): Promise<void>;
}
interface GlobalDataProcessType extends PipcookPlugin {
  (dataset: UniDataset, metadata: Metadata, args: ArgsType): Promise<void>;
}
type DataProcessType = CommonDataProcessType | GlobalDataProcessType;