sage
/
BatterUp
2
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
126 Commits 5 Branches 0 Tags 6.9 MiB
Lua 99.9%
Makefile 0.1%
Go to file
Sage Vaillancourt aceefeb25c Add a screen for showing the game's controls 
Tweak MainMenu appearance to show this new option.
Simple new drawButton() graphics function.
Set a max value for transition delta, to keep from leaving gaps in the mask.
 		2025-02-23 13:10:09 -05:00
lib Add LuaPreprocess for asset-processing. 2025-02-08 01:53:26 -05:00
src Add a screen for showing the game's controls 2025-02-23 13:10:09 -05:00
.gitignore Start up some simple baserunning. 2025-01-26 21:34:19 -05:00
.luacheckrc Add .luacheckrc, remove selene.toml 2025-02-16 18:43:09 -05:00
.luarc.json Add music + sound effects to assets.lua2p 2025-02-08 09:39:56 -05:00
.styluaignore Fix linting 2025-02-09 14:47:37 -05:00
Makefile Use `-v` in `make test` 2025-02-23 11:11:04 -05:00
README.md Backfill with <const> 2025-02-01 17:45:10 -05:00
__stub.ext.lua Add a screen for showing the game's controls 2025-02-23 13:10:09 -05:00

README.md

Batter Up!

Style Guide

This project uses StyLua for linting, and Selene for various other checks.

In addition to using <const>, where applicable, PascalCase is used for any values which should never be mutated, including any elements in a table.

E.g.

local Screen <const> = { x = 400, y = 240 }

should be treated the same as

local ScreenX <const> = 400
local ScreenY <const> = 240

Though the compiler will not enforce this. Furthermore, PascalCase is also used for values that may mutate themselves through method calls. For example, instances of playdate.graphics.animator. The one exception is gfx

N.b. Selene does not understand <const>, so make check uses a sed hack to filter them out.

camelCase tables may be <const>, but can still have mutable fields.