Table: Simplify data flow

RhoInc / Webcharts

Reusable, flexible, interactive charts with JavaScript

MIT License

34 stars 6 forks source link

Table: Simplify data flow #119

Closed jwildfire closed 6 years ago

jwildfire commented 6 years ago

The rarely used config.row_per option routes table data through d3.nest() which causes some complications when implementing search and filter. This issue would do one of 2 things:

1) Eliminate row_per and just have all table.data sub-objects be standard arrays with one object per tr, or ... 2) rework the data flow so that table.data.nested is created based on row_per at the very end of the data manipulation work flow (and can be ignored in most use cases).

jwildfire commented 6 years ago

Proposed Data Flow (in order of creation) - all data sets are one record per row using standard d3.csv format unless noted

raw - all data rows passed to the table
passed (delete) - same as raw
filtered - raw, with filters applied (if any)
search - filtered, with search applied (if any)
current/paginated - search, with pagination (if any)
nested - current, nested by row_per columns

jwildfire commented 6 years ago

Technical change. No user testing needed. Will be covered in regression testing.