Nicolo John Davis

I think we should have agreement on the user data storage part first, because that's a critical design feature. Feel free to implement any of the items that don't touch...

@flamecoals @francoijs @jasonharrison Do you guys have thoughts about what to do about the Lobby in the Svelte world (after #432)? We can migrate the lobby rendering components to Svelte...

Perhaps we should use a generic `render` callback of some sort that the user can use to the render the game using any technology of their choice? #### Current State...

Why would we need to pull in `react-svelte`? Wouldn't the React dependencies be the responsibility of the developer using boardgame.io? ```js import { Lobby } from 'boardgame.io/lobby'; // These are...

`LobbyConnection` is just a simple REST client that invokes our API. Do you think there is much value in making that externally visible? I would think that people would prefer...

My thinking was that we just provide the REST API (which can be consumed in many ways). In addition to that, we also provide a default lobby implementation (that can...

An optional extra function to implement sounds quite reasonable: Something like: ``` (gamestate) => list of next move types with arg ranges ``` perhaps? In fact, given that END_TURN can...

This also takes care of the illegal move problem (the function that the user implements only returns legal moves).

re: handling illegal moves The main reason that I chose to go the current route is because that's how [Redux](https://redux.js.org/docs/basics/Reducers.html) does it, and it's a paradigm that developers are familiar...

I've started a branch [ai](https://github.com/google/boardgame.io/tree/ai) that implements the invalid move logic we talked about. Whenever you're ready, send me a PR to add stuff to this branch with the AI...