v7.0.0-rc.4

The wrong variable was being checked against `undefined`, so the row was
always being toggled, rather than taking the parameter into account.

.size-snapshot.json

@@ -2,12 +2,12 @@
   "dist/index.js": {
     "bundled": 100428,
     "minified": 47447,
-    "gzipped": 12338
+    "gzipped": 12335
   },
   "dist/index.es.js": {
     "bundled": 99612,
     "minified": 46722,
-    "gzipped": 12193,
+    "gzipped": 12189,
     "treeshaked": {
       "rollup": {
         "code": 80,

CHANGELOG.md

@@ -1,3 +1,7 @@
+## 7.0.0-rc.3
+
+- Fixed an issue where `column.clearSortBy` would crash
+
 ## 7.0.0-rc.2
 
 - `reducerHandlers` has been deprecated in favor of the new `stateReducers` hook.

docs/api/useExpanded.md

@@ -35,7 +35,7 @@ The following options are supported via the main options object passed to `useTa
   - When `true`, the `expanded` state will automatically reset if any of the following conditions are met:
     - `data` is changed
   - To disable, set to `false`
-  - For more information see the FAQ ["How do I stop my table state from automatically resetting when my data changes?"](./faq#how-do-i-stop-my-table-state-from-automatically-resetting-when-my-data-changes)
+  - For more information see the FAQ ["How do I stop my table state from automatically resetting when my data changes?"](../faq.md#how-do-i-stop-my-table-state-from-automatically-resetting-when-my-data-changes)
 
 ### Instance Properties
 

docs/api/useFilters.md

@@ -27,10 +27,10 @@ The following options are supported via the main options object passed to `useTa
   - Must be **memoized**
   - Allows overriding or adding additional filter types for columns to use. If a column's filter type isn't found on this object, it will default to using the built-in filter types.
   - For more information on filter types, see Filtering
-- `getResetFiltersDeps: Function(instance) => [...useEffectDependencies]`
-  - Optional
-  - Defaults to `false`
-  - If set, the dependencies returned from this function will be used to determine when the effect to reset the `filters` state is fired.
+- `autoResetFilters: Boolean`
+  - Defaults to `true`
+  - When `true`, the `filters` state will automatically reset if any of the following conditions are met:
+    - `data` is changed
   - To disable, set to `false`
   - For more information see the FAQ ["How do I stop my table state from automatically resetting when my data changes?"](./faq#how-do-i-stop-my-table-state-from-automatically-resetting-when-my-data-changes)
 

docs/faq.md

@@ -28,6 +28,29 @@ useTable({
 
 > **It's important that the state override is done within a `useMemo` call to prevent the state variable from changing on every render. It's also extremely important that you always use the `state` in any dependencies to ensure that you do not block normal state updates.**
 
+## How can I use the table state to fetch new data?
+
+When managing your data externally or asynchronously (eg. server-side pagination/sorting/grouping/etc), you will need to fetch new data as the internal table state changes. With React Hooks, this is fantastically easier than it was before now that we have the `React.useEffect` hook. We can use this hook to "watch" the table state for specific changes and use those effects to trigger fetches for new data (or synchronize any other state you may be managing externally from your table component):
+
+```js
+function Table({ data, onFetchData }) {
+  const {
+    state: { pageIndex, pageSize, sortBy, filters },
+  } = useTable({
+    data,
+  })
+
+  // When the these table states change, fetch new data!
+  React.useEffect(() => {
+    onFetchData({ pageIndex, pageSize, sortBy, filters })
+  }, [fetchData, pageIndex, pageSize, sortBy, filters])
+
+  return </>
+}
+```
+
+Using this approach, you can respond and trigger any type of side-effect using the table instance!
+
 ## How can I debounce rapid table state changes?
 
 React Table has a few built-in side-effects of it's own (most of which are meant for resetting parts of the state when `data` changes). By default, these state side-effects are on and when their conditions are met, they immediately fire off actions that will manipulate the table state. Sometimes, this may result in multiple rapid rerenders (usually just 2, or one more than normal), and could cause any side-effects you have watching the table state to also fire multiple times in-a-row. To alleviate this edge-case, React Table exports a `useAsyncDebounce` function that will allow you to debounce rapid side-effects and only use the latest one.
@@ -58,29 +81,6 @@ function Table({ data, onFetchData }) {
 }
 ```
 
-## How can I use the table state to fetch new data?
-
-When managing your data externally or asynchronously (eg. server-side pagination/sorting/grouping/etc), you will need to fetch new data as the internal table state changes. With React Hooks, this is fantastically easier than it was before now that we have the `React.useEffect` hook. We can use this hook to "watch" the table state for specific changes and use those effects to trigger fetches for new data (or synchronize any other state you may be managing externally from your table component):
-
-```js
-function Table({ data, onFetchData }) {
-  const {
-    state: { pageIndex, pageSize, sortBy, filters },
-  } = useTable({
-    data,
-  })
-
-  // When the these table states change, fetch new data!
-  React.useEffect(() => {
-    onFetchData({ pageIndex, pageSize, sortBy, filters })
-  }, [fetchData, pageIndex, pageSize, sortBy, filters])
-
-  return </>
-}
-```
-
-Using this approach, you can respond and trigger any type of side-effect using the table instance!
-
 ## How do I stop my table state from automatically resetting when my data changes?
 
 Most plugins use state that _should_ normally reset when the data sources changes, but sometimes you need to suppress that from happening if you are filtering your data externally, or immutably editing your data while looking at it, or simply doing anything external with your data that you don't want to trigger a piece of table state to reset automatically.
@@ -119,5 +119,3 @@ useTable({
 ```
 
 Now, when we update our data, the above table states will not automatically reset!
-
-<!-- ## How can I hide/show columns? -->

examples/grouping/yarn.lock

@@ -3652,16 +3652,16 @@ eslint-scope@^4.0.0, eslint-scope@^4.0.3:
     estraverse "^4.1.1"
 
 eslint-utils@^1.3.1:
-  version "1.4.0"
-  resolved "https://registry.yarnpkg.com/eslint-utils/-/eslint-utils-1.4.0.tgz#e2c3c8dba768425f897cf0f9e51fe2e241485d4c"
-  integrity sha512-7ehnzPaP5IIEh1r1tkjuIrxqhNkzUJa9z3R92tLJdZIVdWaczEhr3EbhGtsMrVxi1KeR8qA7Off6SWc5WNQqyQ==
+  version "1.4.3"
+  resolved "https://registry.yarnpkg.com/eslint-utils/-/eslint-utils-1.4.3.tgz#74fec7c54d0776b6f67e0251040b5806564e981f"
+  integrity sha512-fbBN5W2xdY45KulGXmLHZ3c3FHfVYmKg0IrAKGOkT/464PQsx2UeIzfz1RmEci+KLm1bBaAzZAh8+/E+XAeZ8Q==
   dependencies:
-    eslint-visitor-keys "^1.0.0"
+    eslint-visitor-keys "^1.1.0"
 
-eslint-visitor-keys@^1.0.0:
-  version "1.0.0"
-  resolved "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-1.0.0.tgz#3f3180fb2e291017716acb4c9d6d5b5c34a6a81d"
-  integrity sha512-qzm/XxIbxm/FHyH341ZrbnMUpe+5Bocte9xkmFMzPMjRaZMcXww+MpBptFvtU+79L362nqiLhekCxCxDPaUMBQ==
+eslint-visitor-keys@^1.0.0, eslint-visitor-keys@^1.1.0:
+  version "1.1.0"
+  resolved "https://registry.yarnpkg.com/eslint-visitor-keys/-/eslint-visitor-keys-1.1.0.tgz#e2a82cea84ff246ad6fb57f9bde5b46621459ec2"
+  integrity sha512-8y9YjtM1JBJU/A9Kc+SbaOV4y29sSWckBwMHa+FGtVj5gN/sbnKDf6xJUl+8g7FAij9LVaP8C24DUiH/f/2Z9A==
 
 eslint@^5.16.0:
   version "5.16.0"

package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-table",
-  "version": "7.0.0-rc.2",
+  "version": "7.0.0-rc.4",
   "description": "Hooks for building lightweight, fast and extendable datagrids for React",
   "license": "MIT",
   "homepage": "https://github.com/tannerlinsley/react-table#readme",

sizes-cjs.json

@@ -1,4 +1,24 @@
 [
+  {
+    "timestamp": 1575690248030,
+    "files": [
+      {
+        "filename": "index.js",
+        "size": 21026,
+        "delta": 1
+      }
+    ]
+  },
+  {
+    "timestamp": 1575675308812,
+    "files": [
+      {
+        "filename": "index.js",
+        "size": 21025,
+        "delta": -421
+      }
+    ]
+  },
   {
     "timestamp": 1575620433902,
     "files": [

sizes-es.json

@@ -1,4 +1,14 @@
 [
+  {
+    "timestamp": 1575675317538,
+    "files": [
+      {
+        "filename": "index.es.js",
+        "size": 20842,
+        "delta": -383
+      }
+    ]
+  },
   {
     "timestamp": 1575620442742,
     "files": [

src/plugin-hooks/useExpanded.js

@@ -42,7 +42,7 @@ function reducer(state, action) {
     const { path, expanded } = action
     const key = path.join('.')
     const exists = state.expanded.includes(key)
-    const shouldExist = typeof set !== 'undefined' ? expanded : !exists
+    const shouldExist = typeof expanded !== 'undefined' ? expanded : !exists
     let newExpanded = new Set(state.expanded)
 
     if (!exists && shouldExist) {