Magic Yeti

Generated by the Very Good CLI 🤖

Magic The Gathering Tracking App

---

Getting Started 🚀

This project contains 3 flavors:

• development
• staging
• production

To run the desired flavor either use the launch configuration in VSCode/Android Studio or use the following commands:

# Development
$ flutter run --flavor development --target lib/main_development.dart

# Staging
$ flutter run --flavor staging --target lib/main_staging.dart

# Production
$ flutter run --flavor production --target lib/main_production.dart

*Magic Yeti works on iOS, Android, Web, and Windows.

---

Running Tests 🧪

To run all unit and widget tests use the following command:

$ flutter test --coverage --test-randomize-ordering-seed random

To view the generated coverage report you can use lcov.

# Generate Coverage Report
$ genhtml coverage/lcov.info -o coverage/

# Open Coverage Report
$ open coverage/index.html

---

Working with Translations 🌐

This project relies on flutter_localizations and follows the official internationalization guide for Flutter.

Adding Strings

1. To add a new localizable string, open the app_en.arb file at lib/l10n/arb/app_en.arb.

{
    "@@locale": "en",
    "counterAppBarTitle": "Counter",
    "@counterAppBarTitle": {
        "description": "Text shown in the AppBar of the Counter Page"
    }
}

2. Then add a new key/value and description

{
    "@@locale": "en",
    "counterAppBarTitle": "Counter",
    "@counterAppBarTitle": {
        "description": "Text shown in the AppBar of the Counter Page"
    },
    "helloWorld": "Hello World",
    "@helloWorld": {
        "description": "Hello World Text"
    }
}

3. Use the new string

import 'package:magic_yeti/l10n/l10n.dart';

@override
Widget build(BuildContext context) {
  final l10n = context.l10n;
  return Text(l10n.helloWorld);
}

Adding Supported Locales

Update the CFBundleLocalizations array in the Info.plist at ios/Runner/Info.plist to include the new locale.

    ...

    <key>CFBundleLocalizations</key>
	<array>
		<string>en</string>
		<string>es</string>
	</array>

    ...

Adding Translations

1. For each supported locale, add a new ARB file in lib/l10n/arb.

├── l10n
│   ├── arb
│   │   ├── app_en.arb
│   │   └── app_es.arb

2. Add the translated strings to each .arb file:

app_en.arb

{
    "@@locale": "en",
    "counterAppBarTitle": "Counter",
    "@counterAppBarTitle": {
        "description": "Text shown in the AppBar of the Counter Page"
    }
}

app_es.arb

{
    "@@locale": "es",
    "counterAppBarTitle": "Contador",
    "@counterAppBarTitle": {
        "description": "Texto mostrado en la AppBar de la página del contador"
    }
}

Generating Translations

To use the latest translations changes, you will need to generate them:

1. Generate localizations for the current project:

flutter gen-l10n --arb-dir="lib/l10n/arb"

Alternatively, run flutter run and code generation will take place automatically.

---

Firebase Backend 🔥

Magic Yeti's backend lives alongside the Flutter app in this repo:

• functions/ — TypeScript Cloud Functions (e.g. validatePin, a callable that checks a user's PIN server-side against their salted private credentials).
• firestore.rules — Firestore security rules governing direct client reads and writes (friends, requests, profiles, private credentials, etc.).

Running backend tests

# Build and unit test the Cloud Functions
cd functions && npm run build && npm test && cd ..

# Run the firebase_database_repository package tests
cd packages/firebase_database_repository && flutter test && cd ..

# Run Firestore security rules tests against the emulator
firebase emulators:exec --only firestore "npm --prefix functions run test:rules"

If the globally-installed firebase CLI has trouble with emulators:exec, pin a known-good version instead:

npx firebase-tools@14.9.0 emulators:exec --only firestore "npm --prefix functions run test:rules"

Deploying

firebase deploy --only firestore:rules,functions

Deploys are run manually by a maintainer — see docs/superpowers/plans/2026-07-03-friends-INDEX.md for the pre-deploy gate (diffing versioned rules against the console's current production rules before the first deploy).