[New UI] Unity Build in React

[OlafSzmidt]

When merging, merge this along with PR: ocadotechnology/aimmo-unity#211.

Some of the changes:

• Docs changed
• Parcel is now not minifying code as well as caching has been disabled.
• Introduces 3rd party react-unity-webgl package.
• Makes use of the helper function @mrniket wrote for snapshot testing in current tests.
• We register an external listener for a function here SendAllConnect() and we dispatch calls to Unity's webGL build too.
• New reducer, new store format, loads of new types.
• API used in our epics for unity slightly changed. It's parameterised for a generic case but we left epics separate.
• Little refactoring of players in aimmo.

Things that could be improved and we should discuss for future:

• Error catching. Right now our React has very little error catching. Some of the stuff I've added here is also poorly caught. We sometimes use catchError() but even then we don't use the error object to use that information. Even worse, we can have a success action in redux being returned by the epic but when we emit a certain function call to Unity, SendMessage() call might fail and we have no way of catching that through the redux stuff?
• Marble tests are probably incorrect for the epics. At first when I had two marbles, with events at frame 10 everything was fine. Now even when the first event, a, is dispatched at frame 10, the success response happens at frame 0. It also completes, which we probably don't want to happen. Unsure what's happening here. Tests passing right now because I emit the first event at 0 and expect a success and completion at 0 as well.
• Styling is completely wrong. When resizing after the WebGL loads the website goes crazy.

---

This change is 

[CelineBoudier]

the tests fail

[OlafSzmidt]

Review status: 23 of 32 files reviewed, 7 unresolved discussions (waiting on @mrniket, @riaJha97, @OlafSzmidt, and @CelineBoudier)

---

players/tests.py, line 321 at r10 (raw file):

Previously, OlafSzmidt (Olaf Szmidt) wrote…

I guess it can cause confusion between two meanings: avatar_ID and game_ID. I'll try to change it back.

Done.

---

Comments from Reviewable

[OlafSzmidt]

Review status: 23 of 32 files reviewed, 7 unresolved discussions (waiting on @mrniket, @riaJha97, @OlafSzmidt, and @CelineBoudier)

---

game_frontend/src/redux/features/Game/epics.test.js, line at r10 (raw file):

Previously, mrniket (Niket Shah) wrote…

I see your point. I guess the better way to test this would we should write tests for the api/unity folder. That way you could mock the SendMessage unity call and check that it returns the "fail" action

Don't think we can mock SendMessage() either. It's used here, look:

https://github.com/ocadotechnology/aimmo-unity/blob/b9eaba7a46f7cd57f3e03a8d2a4972747298820c/UnityProject/Assets/Scripts/UnitySocketIO/SocketIOWrapper.jslib

Instead, maybe we should handle errors on the Unity side and propagate them back to React somehow. No idea how.

---

Comments from Reviewable

[mrniket]

Reviewed 9 of 9 files at r14.
Review status: all files reviewed, 1 unresolved discussion (waiting on @mrniket)

---

game_frontend/djangoBundler.js, line 15 at r13 (raw file):

Previously, OlafSzmidt (Olaf Szmidt) wrote…

You mean === if it's false we're expecting locally right (in non prod environments). If yes, done.

ah sorry, yes :)

---

game_frontend/src/redux/features/Game/epics.test.js, line at r10 (raw file):

https://github.com/ocadotechnology/aimmo-unity/blob/b9eaba7a46f7cd57f3e03a8d2a4972747298820c/UnityProject/Assets/Scripts/UnitySocketIO/SocketIOWrapper.jslib

Quick aside: that's the wrapper we plan to remove (in a separate issue) when we start listening for websocket events through the frontend instead of through unity, right?

Sorry, I referred to the wrong thing. I was talking about emitToUnity in api/unity.js as the method that we could perhaps mock for api/unity.js tests

---

Comments from Reviewable

[CelineBoudier]

Reviewed 1 of 10 files at r8, 1 of 11 files at r13.
Review status: all files reviewed, 1 unresolved discussion (waiting on @OlafSzmidt)

---

players/utilities.py, line 1 at r10 (raw file):

Previously, OlafSzmidt (Olaf Szmidt) wrote…

So I'm happy to just resolve this if you are

helpers just sounds the same as utilities to me :/ I'd go with Niket's suggestion tbh

---

Comments from Reviewable

[CelineBoudier]

---

Review status: all files reviewed, 1 unresolved discussion (waiting on @OlafSzmidt)

---

Comments from Reviewable

[mrniket]

---

Review status: all files reviewed, 1 unresolved discussion (waiting on @OlafSzmidt)

---

Comments from Reviewable

[OlafSzmidt]

Review status: all files reviewed, 1 unresolved discussion (waiting on @OlafSzmidt)

---

players/utilities.py, line 1 at r10 (raw file):

Previously, CelineBoudier (Celine Boudier) wrote…

helpers just sounds the same as utilities to me :/ I'd go with Niket's suggestion tbh

Done.

---

Comments from Reviewable

[CelineBoudier]

---

Review status: 30 of 32 files reviewed, 1 unresolved discussion (waiting on @CelineBoudier, @mrniket, @riaJha97, and @OlafSzmidt)

---

Comments from Reviewable

[CelineBoudier]

Reviewed 1 of 2 files at r15.
Review status: 31 of 32 files reviewed, 1 unresolved discussion (waiting on @mrniket and @OlafSzmidt)

---

Comments from Reviewable

[CelineBoudier]

Reviewed 1 of 2 files at r15.
Review status: all files reviewed, 1 unresolved discussion (waiting on @OlafSzmidt)

---

Comments from Reviewable

[mrniket]

Reviewed 1 of 2 files at r15, 1 of 34 files at r19.
Review status: 1 of 36 files reviewed, all discussions resolved (waiting on @CelineBoudier, @mrniket, @riaJha97, and @OlafSzmidt)

---

Comments from Reviewable

[mrniket]

Reviewed 1 of 36 files at r17, 1 of 1 files at r18, 33 of 34 files at r19.
Review status: complete! all files reviewed, all discussions resolved

---

Comments from Reviewable