-
Notifications
You must be signed in to change notification settings - Fork 396
Development Tips and Tricks
Start the REPL with lein repl.
When you modify a card, use your repl to evaluate the defcard block. Because it's a multi-method, all future uses of card-def in the engine will use the updated code. For cards already installed you have to drag it back to hand and install it again to reflect the new code. No need to refresh the browser, you can keep the game state.
Changes to core game functions will require restarting the REPL. I don't believe this is true anymore, but it requires more testing.
To inspect the content of Clojure data structures, prn is handy. You can add prn in your functions or inside the (req ) macro in card definitions you want to inspect.
Once a game is started, execute:
(def state (:state (second (first @all-games))))
You can then use state to inspect the current game state, the same as if you were in a card our core function. Execute the def again when you make a new game.
As an example, you can then run
(pprint (core/all-installed state :corp))
to list all installed corp cards.
To modify the client side, Figwheel is awesome. Run lein figwheel and stylus -w src/css -o resources/public/css/. When you save a .cljs or .styl file, the Clojurescript or Stylus is automatically compiled and sent to the connected browsers. No need to refresh anything, you keep the game state. When you have an error in a .cljs file, the UI might disappear. Don't panic! As soon as the error is corrected the UI will reappear. No need to reload anything.
To run the unit tests: lein test
Tests are in the game-test namespace. To run selected unit tests: lein test game.cards.agendas-test
To combine test and repl run: lein clean && lein test && lein repl. This makes sure no compiled files are left from a branch switch or similar, and only starts the repl if all the tests pass.