CK Student Council Legistaive Platform (cksc-platform)

A legislative platform with punch-in, voting and legal code keeping features

Install the dependencies

yarn
# or
npm install

Start the app in development mode (hot-code reloading, error reporting, etc.)

quasar dev

Lint the files

yarn lint
# or
npm run lint

Format the files

yarn format
# or
npm run format

Build the app for production

quasar build

Customize the configuration

See Configuring quasar.config.js.

Error monitoring (Sentry)

Runtime errors are reported to the cksc/platform Sentry project. Reporting is initialised in src/boot/sentry.ts and is disabled during quasar dev so local work does not add noise — flip enabled in that boot file if you need to verify it locally.

Everything the browser needs (the DSN) is committed in shared/constants.ts; it is a public, write-only identifier, exactly like FIREBASE_CONFIG.

Uploading source maps, so stack traces are readable instead of minified, is a CI-only step. quasar.config.ts enables it when all three of these are present in the environment, and skips it silently otherwise:

Name	Where it lives	Value
SENTRY_ORG	GitHub repo variable	cksc
SENTRY_PROJECT	GitHub repo variable	platform
SENTRY_AUTH_TOKEN	GitHub repo secret	Org token with project:releases

The deploy workflow (pages-deploy-merge.yml) passes all three. PR builds deliberately do not, since they are never deployed. To rotate the token, create a new one under Organization Auth Tokens and update the repository secret — an invalid token only downgrades stack trace quality, it will not fail the deploy.