Update STYLE_GUIDE to reflect nextAction methodology

docs/STYLE_GUIDE.md

@@ -65,6 +65,30 @@ src
 
 We use the [Flux Standard Action](https://github.com/redux-utilities/flux-standard-action) as a standard for our redux actions.
 
+To dispatch actions on sagas, we use a slightly different approach. By attaching the nextAction(s) on the meta prop of each action, we can completely customise and chain our actions on the fly, without having to write more explicit sagas, i.e:
+
+```js
+this.props.dispatch({
+	type: 'getAuth',
+	meta: {
+		nextAction: {
+			type: 'SIGN_IN_USER',
+			payload: {
+				...
+			},
+			meta: {
+				nextAction: {
+					type: 'SET_SYSTEM_MESSAGE',
+					payload: {
+						message: 'Sign in successful'
+					}
+				}
+			}
+		}
+	}
+})
+```
+
 ## Terminology
 
 Some common terminology that we use.

docs/TESTING.md

@@ -60,7 +60,9 @@ it('renders a SmartImage with offline error', () => {
 
 ### Testing sagas
 
-#### Typical types of tests carried out
+Don't be alarmed when looking at these tests, there are distinct patterns.
+
+#### Patterns
 
 - Testing the saga without a nextAction and without a response from the api
 - Testing the saga without a nextAction and with a response from the api