Currently, workflows are only run whenever an event in a pull_request occurs. I think we also should run the workflows on the push event to get more immediate feedback about the code we are working on, without having to make a pull request for it.

Right now, the badge links to https://github.com/hexil-org/hexer/actions/workflows/check.yaml. But it should link to https://github.com/hexil-org/hexer/actions/workflows/deploy.yaml instead.

When three players are connected, a game should start. A random permutation of players should be generated.

Then the first player gets the turn. When the first player ends the turn, the second player gets the turn. And so forth.

When a player disconnects, the game ends.

Depends on #5.

We will need a program to check the coverage.

Options:

• grcov (by Mozilla, kinda big, is not only for Rust, crossplatform)
• tarpaulin (looks like it's easy to use, only linux)
• cargo-llvm-cov (simple installation, simple usage (just run cargo llvm-cov), only line coverage, crossplatform)

The following information should be encapsulated in HSN:

• The map / static part of the board:

  • Which tile kinds where
  • Which resource numbers where
  • Which harbors where

• The dynamic part of the board:

  • The location of the robber
  • Which villages/cities are placed where
  • Which roads are placed where

• About the players (including the bank as player 0):

  • The resources that each player holds

  • The development cards each player holds (excluding any cards bought in the current turn)

  • The number of knights each player used

  • Which player has the largest army

  • Which player has the longest road

• About the current turn:

  • The turn number
  • Whether or not the current player already rolled
  • Whether or not a development card was played
  • Whether or not the current player must steal now
  • Whether or not the current player must move the robber now
  • Which players still must discard half their cards now
  • Which development cards were bought this turn
  • Which items (roads, cities, villages) the player may place immediately (road building card)
  • Which items (roads, cities, villages) the player must place immediately (start of game, buying)

Send the HAN E on the end of the turn, instead of using a custom message for that. Ignore any other HAN messages for now.

The client of the current player may send the action E to the backend. In that case, the action E will be broadcasted to all clients, and it's the next players turn.

This pull request changes the asset bundler from Webpack to Laravel Mix. Laravel Mix is an abstraction on top op Webpack, making it easier to use. It still provides low level control over the resulting Webpack config through its API.

According to the Webpack documentation (https://webpack.js.org/guides/production/):

Technically, NODE_ENV is a system environment variable that Node.js exposes into running scripts. It is used by convention to determine dev-vs-prod behavior by server tools, build scripts, and client-side libraries.

The current transpilation target set in front/tsconfig.json is ECMAScript 5. The benefit of using ECMAScript 5 is that compatibility with older browsers is better, however, for this we give up on performance and many modern features (such as the let and const keyword). Since we already use ECMAScript 6 as the module, all these features have to be transpiled into ES5 code, which can introduce several issues. For example, I was working on a custom element for the frontend, and eventhough the TypeScript compiled, the target JavaScript was not valid and gave errors when ran in a browser.

If we look at the caniuse.com matrix for ECMAScript, we see it is supported by the following major browsers:

• Chrome 51 or higher (2016)
• Edge 15 or higher (2017)
• Safari 10 or higher (2016)
• Firefox 54 or higher (2017)
• Opera 38 or higher (2016)
• Some other minor/mobile browsers...

The total support percentage is 98.34%. The notable exception is that ECMAScript 6 is not fully supported by Internet Explorer.

Use npm ci instead of npm install in the docker build (front/Dockerfile).

https://docs.npmjs.com/cli/v8/commands/npm-ci:

This command is similar to npm install, except it's meant to be used in automated environments such as test platforms, continuous integration, and deployment -- or any situation where you want to make sure you're doing a clean install of your dependencies.

In order to make Hexil a one-page webapp, we need to make a client-side router. In order to facilitate this, we need to make a few configuration changes in the server:

• All routes need to be routed to index.html
• With the exception of certain routes such as /static/*

The frontend should at any time show:

• which player you are
• which player's turn it is right now

If it's currently your turn, it must present you with the option to end that turn.