Death of the path, fix some hooks, fix selectedRows

- Fixed an issue where dependency hooks were not being reduced properly, thus the table would rerender unnecessarily
- Renamed `toggleRowSelectedAll` to `toggleAllRowsSelected`. Duh...
- Added an `indeterminate` boolean prop to the default props for row selection toggle prop getters
- Renamed `selectedRowPaths` to `selectedRowIds`, which also no longer contains paths, but row IDs
- Grouped or nested row selection actions and state are now derived, instead of tracked in state.
- Rows now have a new property called `id`, which existed before and was derived from the `getRowId` option
- Rows now also have an `isSomeSelected` prop when using the `useRowSelect` hook, which denotes that at least one subRow is selected (if applicable)
- Rows' `path` property has been deprecated in favor of `id`
- Expanded state is now tracked with row IDs instead of paths
- RowState is now tracked with row IDs instead of paths
- `toggleExpandedByPath` has been renamed to `toggleExpandedById`, and thus accepts a row ID now, instead of a row path

docs/api/useExpanded.md

@@ -9,12 +9,12 @@
 
 The following options are supported via the main options object passed to `useTable(options)`
 
-- `state.expanded: Array<pathKey: String>`
+- `state.expanded: Array<rowId: String>`
   - Optional
   - Must be **memoized**
-  - An array of expanded path keys.
-  - If a row's path key (`row.path.join('.')`) is present in this array, that row will have an expanded state. For example, if `['3']` was passed as the `expanded` state, the **4th row in the original data array** would be expanded.
-  - For nested expansion, you may **join the row path with a `.`** to expand sub rows. For example, if `['3', '3.5']` was passed as the `expanded` state, then the **6th subRow of the 4th row and also the 4th row of the original data array** would be expanded.
+  - An array of expanded row IDs.
+  - If a row's id is present in this array, that row will have an expanded state. For example, if `['3']` was passed as the `expanded` state, by default the **4th row in the original data array** would be expanded, since it would have that ID
+  - For nested expansion, you can **use nested IDs like `1.3`** to expand sub rows. For example, if `['3', '3.5']` was passed as the `expanded` state, then the **the 4th row would be expanded, along with the 6th subRow of the 4th row as well**.
   - This information is stored in state since the table is allowed to manipulate the filter through user interaction.
 - `initialState.expanded`
   - Identical to the `state.expanded` option above

docs/api/useGroupBy.md

@@ -96,9 +96,11 @@ The following properties are available on every `Row` object returned by the tab
   - If the row is a materialized group row, this property is the array of materialized subRows that were grouped inside of this row.
 - `depth: Int`
   - If the row is a materialized group row, this is the grouping depth at which this row was created.
-- `path: Array<String|Int>`
-  - Similar to normal `Row` objects, materialized grouping rows also have a path array. The keys inside it though are not integers like nested normal rows though. Since they are not rows that can be traced back to an original data row, they are given a unique path based on their `groupByVal`
-  - If a row is a grouping row, it will have a path like `['Single']` or `['Complicated', 'Anderson']`, where `Single`, `Complicated`, and `Anderson` would all be derived from their row's `groupByVal`.
+- `id: String`
+  - The unique ID for this row.
+  - This ID is unique across all rows, including sub rows
+  - Derived from the `getRowId` function, which defaults to chaining parent IDs and joining with a `.`
+  - If a row is a materialized grouping row, it will have an ID in the format of `columnId:groupByVal`.
 - `isAggregated: Bool`
   - Will be `true` if the row is an aggregated row
 

docs/api/useRowSelect.md

@@ -9,12 +9,10 @@
 
 The following options are supported via the main options object passed to `useTable(options)`
 
-- `state.selectedRowPaths: Set<RowPathKey>`
+- `initialState.selectedRowIds: Set<RowPathKey>`
   - Optional
   - Defaults to `new Set()`
-  - If a row's path key (eg. a row path of `[1, 3, 2]` would have a path key of `1.3.2`) is found in this array, it will have a selected state.
-- `initialState.selectedRowPaths`
-  - Identical to the `state.selectedRowPaths` option above
+  - If a row's ID is found in this array, it will have a selected state.
 - `manualRowSelectedKey: String`
   - Optional
   - Defaults to `isSelected`
@@ -33,7 +31,7 @@ The following values are provided to the table `instance`:
 - `toggleRowSelected: Function(rowPath: String, ?set: Bool) => void`
   - Use this function to toggle a row's selected state.
   - Optionally pass `true` or `false` to set it to that state
-- `toggleRowSelectedAll: Function(?set: Bool) => void`
+- `toggleAllRowsSelected: Function(?set: Bool) => void`
   - Use this function to toggle all rows as select or not
   - Optionally pass `true` or `false` to set all rows to that state
 - `getToggleAllRowsSelectedProps: Function(props) => props`
@@ -55,6 +53,8 @@ The following additional properties are available on every **prepared** `row` ob
 
 - `isSelected: Bool`
   - Will be `true` if the row is currently selected
+- `isSomeSelected: Bool`
+  - Will be `true` if the row has subRows and at least one of them is currently selected
 - `toggleRowSelected: Function(?set)`
   - Use this function to toggle this row's selected state.
   - Optionally pass `true` or `false` to set it to that state

docs/api/useRowState.md

@@ -12,7 +12,7 @@ The following options are supported via the main options object passed to `useTa
 - `state.rowState: Object<RowPathKey:Object<any, cellState: {columnId: Object}>>`
   - Optional
   - Defaults to `{}`
-  - If a row's path key (eg. a row path of `[1, 3, 2]` would have a path key of `1.3.2`) is found in this array, it will have the state of the value corresponding to that key.
+  - If a row's ID is found in this array, it will have the state of the value corresponding to that key.
   - Individual row states can contain anything, but they also contain a `cellState` key, which provides cell-level state based on column ID's to every
     **prepared** cell in the table.
 - `initialState.rowState`
@@ -44,7 +44,7 @@ The following values are provided to the table `instance`:
 The following additional properties are available on every **prepared** `row` object returned by the table instance.
 
 - `state: Object`
-  - This is the state object for each row, pre-mapped to the row from the table state's `rowState` object via `rowState[row.path.join('.')]`
+  - This is the state object for each row, pre-mapped to the row from the table state's `rowState` object via `rowState[row.id]`
   - May also contain a `cellState` key/value pair, which is used to provide individual cell states to this row's cells
 - `setState: Function(updater: Function | any)`
   - Use this function to programmatically update the state of a row.
@@ -55,7 +55,7 @@ The following additional properties are available on every **prepared** `row` ob
 The following additional properties are available on every `Cell` object returned in an array of `cells` on every row object.
 
 - `state: Object`
-  - This is the state object for each cell, pre-mapped to the cell from the table state's `rowState` object via `rowState[row.path.join('.')].cellState[columnId]`
+  - This is the state object for each cell, pre-mapped to the cell from the table state's `rowState` object via `rowState[row.id].cellState[columnId]`
 - `setState: Function(updater: Function | any)`
   - Use this function to programmatically update the state of a cell.
   - `updater` can be a function or value. If a `function` is passed, it will receive the current value and expect a new one to be returned.

docs/api/useTable.md

@@ -53,13 +53,11 @@ The following options are supported via the main options object passed to `useTa
   - Defaults to `(row) => row.subRows || []`
   - Use this function to change how React Table detects subrows. You could even use this function to generate sub rows if you want.
   - By default, it will attempt to return the `subRows` property on the row, or an empty array if that is not found.
-- `getRowId: Function(row, relativeIndex) => string`
-  - Use this function to change how React Table detects unique rows and also how it constructs each row's underlying `path` property.
+- `getRowId: Function(row, relativeIndex, ?parent) => string`
+  - Use this function to change how React Table detects unique rows and also how it constructs each row's underlying `id` property.
   - Optional
   - Must be **memoized**
-  - Defaults to `(row, relativeIndex) => relativeIndex`
-  - You may want to change this function if
-  - By default, it will use the `index` of the row within it's original array.
+  - Defaults to `(row, relativeIndex, parent) => parent ? [parent.id, relativeIndex].join('.') : relativeIndex`
 - `debug: Bool`
   - Optional
   - A flag to turn on debug mode.
@@ -255,9 +253,6 @@ The following additional properties are available on every `row` object returned
   - The index of the original row in the `data` array that was passed to `useTable`. If this row is a subRow, it is the original index within the parent row's subRows array
 - `original: Object`
   - The original row object from the `data` array that was used to materialize this row.
-- `path: Array<string>`
-  - This array is the sequential path of indices one could use to navigate to it, eg. a row path of `[3, 1, 0]` would mean that it is the **first** subRow of a parent that is the **second** subRow of a parent that is the **fourth** row in the original `data` array.
-  - This array is used with plugin hooks like `useExpanded` and `useGroupBy` to compute expanded states for individual rows.
 - `subRows: Array<Row>`
   - If subRows were detect on the original data object, this will be an array of those materialized row objects.
 - `state: Object`