Default data value is now undefined instead of null

Author: tannerlinsley

CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.3.26
+
+- By default the initial state for `data` is now `undefined` instead of `null`, allowing for use of default parameters in destructuring. While this may technically be a "breaking" change, it's more of a bug in spirit as it was not intended to be shipped this way. Don't like this? Become a sponsor and demand otherwise ;)
+
 ## 0.3.25
 
 - Fixed an issue where `cancelQueries` was called while not being defined

README.md

@@ -1333,7 +1333,7 @@ const {
   - When `true`, `useQuery` will throw runtime errors when `error` would normally be truthy
 - `initialData: any`
   - Optional
-  - If set, this value will be used as the initial data for the query (as long as the query hasn't been created or cached yet)
+  - If set, this value will be used as the initial data for the query cache (as long as the query hasn't been created or cached yet)
 
 ### Returns
 

src/index.js

@@ -88,7 +88,7 @@ function useConfigContext() {
 }
 
 function makeQuery(options) {
-  let initialData = options.config.paginated ? [] : null
+  let initialData = options.config.paginated ? [] : undefined
 
   if (typeof options.config.initialData !== 'undefined') {
     initialData = options.config.initialData