Extra step 3 using this relationship in the frontend - Thewessen/tic-tac-toe_ruby_backend GitHub Wiki

I still wasn't sure about how bindings work in the frontend, so I wanted to try out facing myself with some extra binding problems: creating a new controller, a new route and (ofcourse) a new model. I also intended to make a new service for this, but in the end it felt overkill.

The only way I could find to make the initial game data available in the nicknames model was by utilizing the logic service I already created. Giving it the model data instead of the boardstate, I could simple fetch the model data from the game from the service in the nicknames controller. It feels like going the round-about way. I would not be suprised if their is a much cleaner way, but I couldn't find it.

After this problem, I faced the problem of data not being ready after a redirect. Again the logic service came to the rescue.

Redirecting also had the problem that after refreshing, my newly created game was gone, and I was at a round that depended on a newly created game. My app broke. To solve this, I had to do some check in every routes controller, and redirect where needed. The redirects work very quickly, and because it's a frontend framework, I suspect it keeps working fast in production.