docs about version 3.0

Author: marshallswain

docs/.vuepress/config.js

@@ -9,6 +9,7 @@ module.exports = {
     editLinks: true,
     sidebar: [
       '/api-overview.md',
+      '/3.0-major-release.md',
       '/vue-plugin.md',
       '/service-plugin.md',
       '/auth-plugin.md',
@@ -19,7 +20,7 @@ module.exports = {
       '/data-components.md',
       '/feathers-vuex-form-wrapper.md',
       '/nuxt.md',
-      '/2.0-major-release.md'
+      '/2.0-major-release.md',
     ],
     serviceWorker: {
       updatePopup: true

docs/3.0-major-release.md

@@ -0,0 +1,52 @@
+---
+title: What's New in 3.0
+sidebarDepth: 3
+---
+
+# What's new in Feathers-Vuex 3.0
+
+## Vue Composition API Support
+
+Version 3.0 of Feathers-Vuex is the Vue Composition API release!  There were quite a few disappointed (and misinformed:) developers in 2019 when the Vue.js team announced what is now called the Vue Composition API.  From my perspective:
+
+- It is the most powerful feature added to Vue since its first release.
+- It improves the ability to create dynamic functionality in components.
+- It greatly enhances organization of code in components.
+- It encourages code re-use. Check out the [vue-use-web](https://logaretm.github.io/vue-use-web/) collection for some great examples.
+
+And now it has become the best way to perform queries with Feathers-Vuex.  To find out how to take advantage of the new functionality in your apps, read the [Feather-Vuex Composition API docs](./composition-api.md).
+
+## A Single Breaking Change
+
+Since Feathers-Vuex follows semantic versioning, a single, small breaking change is the reason for the major version bump. Feathers-Vuex 3.0 has only one breaking change:
+
+The `makeFindMixin` (and the new `useFind` utility) now have server-side pagination support turned off, by default.  Real-time arrays of results are now the default setting.  This really improves the development experience, especially for new users.
+
+To migrate your app to version 3.0, you need to update any `params` where you are using server-side pagination.  It will work as it has been in version 2.0 once you explicitly set `paginate: true` in the params, like this:
+
+```js
+import { makeFindMixin } from 'feathers-vuex'
+
+export default {
+  name: 'MyComponent',
+  mixins: [ makeFindMixin({ service: 'users', watch: true })],
+  computed: {
+    usersParams() {
+      return {
+        query: {},
+        paginate: true // explicitly enable pagination, now.
+      }
+    }
+  }
+}
+```
+
+That's the only breaking change in this release.  This behavior exactly matches the new `useFind` utility.
+
+## One Deprecation
+
+The `keepCopiesInStore` option is now deprecated.  This was a part of the "clone and commit" API which basically disabled the reason for creating the "clone and commit" API in the first place.
+
+If you're not familiar with the Feathers-Vuex "clone and commit" API, you can learn more about the [built-in data modeling](./model-classes.md) API and the section about [Working with Forms](./feathers-vuex-form-wrapper.md#the-clone-and-commit-pattern).
+
+The `keepCopiesInStore` feature is set to be removed in Feathers-Vuex 4.0.

docs/feathers-vuex-form-wrapper.md

@@ -25,7 +25,31 @@ The "Clone and Commit" pattern provides an alternative to using a lot of mutatio
 2. Create and modify a clone of the data.
 3. Use a single mutation to commit the changes back to the original record in the store.
 
-Send most edits through a single mutation can really simplify the way you work with Vuex data.  The Feathers-Vuex `BaseModel` class has `clone` and `commit` instance methods.  Those methods are used inside the FeathersVuexFormWrapper component.
+Sending most edits through a single mutation can really simplify the way you work with Vuex data.  The Feathers-Vuex `BaseModel` class has `clone` and `commit` instance methods.   These methods provide a clean API for working with items in the Vuex store and supporting Vuex strict mode:
+
+```js
+import { models } from 'feathers-vuex'
+
+export default {
+  name: 'MyComponent',
+  created() {
+    const { Todo } = models.api
+
+    const todo = new Todo({
+      description: 'Plant the garden',
+      isComplete: false
+    })
+
+    const todoClone = todo.clone()
+    todoClone.description = 'Plant half of the garden."
+    todoClone.commit()
+  }
+}
+```
+
+In the example above, modifying the `todo` variable would directly modify part of the Vuex store outside of a mutation (also known as a reducer in Redux), which is a generally unsupportive practice.  Calling `todo.clone()` returns a reactive clone of the instance and keeps it outside the Vuex store.  This means you can make changes to it all you want without causing any trouble with Vuex.  You can then call `todoClone.commit()` to update the original record in the store.
+
+The `clone` and `commit` methods are used inside the FeathersVuexFormWrapper component.
 
 ## FeathersVuexFormWrapper