|
|
@ -318,6 +318,10 @@ None. |
|
|
|
so that offline-only game can work in all browsers fully supporting Web Components |
|
|
|
so that offline-only game can work in all browsers fully supporting Web Components |
|
|
|
(i.e. Blink-based and Firefox not older than 2018); |
|
|
|
(i.e. Blink-based and Firefox not older than 2018); |
|
|
|
right now ES2022 is targeted. |
|
|
|
right now ES2022 is targeted. |
|
|
|
|
|
|
|
* Figure out better API for game board, |
|
|
|
|
|
|
|
`board.get(row, column)` and `board.get(row, column)` seemed to be a good way to encapsulate readonly state, |
|
|
|
|
|
|
|
but they became very inconvenient as the codebase grew and became more complex, |
|
|
|
|
|
|
|
considering that board does not even expose its dimensions. |
|
|
|
* Figure out better and more consistent naming and project structure. |
|
|
|
* Figure out better and more consistent naming and project structure. |
|
|
|
* Implement end-to-end tests with puppeteer / chromedriver (and run them both with JS enabled and with JS disabled). |
|
|
|
* Implement end-to-end tests with puppeteer / chromedriver (and run them both with JS enabled and with JS disabled). |
|
|
|
* Implement unit tests for remaining shared code. |
|
|
|
* Implement unit tests for remaining shared code. |
|
|
|