Document the new auth getters

Author: marshallswain

docs/3.0-major-release.md

@@ -20,9 +20,19 @@ And now it has become the best way to perform queries with Feathers-Vuex.  To fi
 
 Version 3.1 of Feathers-Vuex enables ability to add custom handling for each of the FeathersJS realtime events.  You can read more about it in the [Service Plugin: Events](./service-plugin.md#service-events) docs.
 
-## A Single Breaking Change
+## Breaking Changes
 
-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:
+Feathers-Vuex follows semantic versioning.  There are two breaking changes in this release:
+
+### Auth Plugin `user` Not Reactive <Badge text="3.2.0+" />
+
+Due to changes in how reactivity is applied to service state (it's now using Vue.set under the hood), the `user` state of the `auth` module is no longer reactive.  To fix this issue, two getters have been added to the `auth` state.  They are available when a `userService` is provided to the `makeAuthPlugin` options.
+
+- `user`: returns the reactive, logged-in user from the `userService` specified in the options.
+- `isAuthenticated`: a easy to remember boolean attribute for if the user is logged in.
+
+
+### Server-Side Pagination Support is Off by Default
 
 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.
 

docs/auth-plugin.md

@@ -40,6 +40,13 @@ It includes the following state by default:
 }
 ```
 
+## Getters
+
+Two getters are available when a `userService` is provided to the `makeAuthPlugin` options.
+
+- `user`: returns the reactive, logged-in user from the `userService` specified in the options.
+- `isAuthenticated`: a easy to remember boolean attribute for if the user is logged in.
+
 ## Actions
 
 The following actions are included in the `auth` module.  Login is accomplished through the `authenticate` action.  For logout, use the `logout` action.  It's important to note that the records that were loaded for a user are NOT automatically cleared upon logout.  Because the business logic requirements for that feature would vary from app to app, it can't be baked into Feathers-Vuex.  It must be manually implemented.  The recommended solution is to simply refresh the browser, which clears the data from memory.