Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

mtg frontend: every Switch emerald

Closed Beginner friendly
  • Is something wrong?
#185 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript
Domain
frontend

Research direction

Read CODING_STANDARDS.md and inspect Switch usages under frontend/mtg/src, including the listed route and component files. Update each Switch to use emerald, then verify every Switch in that directory meets the acceptance criterion. Add a Release note fragment; optionally add an ast-grep rule under .ast-grep/rules and run just lint-ast.

Written by the indexing model from the issue text.

Description

needs-triage

CODING_STANDARDS.md now asks for color={"emerald"} on every Switch in mtg (changed on the deck Collaborators branch, #155). Most Switches predate the rule and still use other colours:

  • 21 Switches use lime (e.g. deck-rule-zero-dialog.tsx, proxy-printer.tsx, cardmarket-settings.tsx, profile/_profile/settings.tsx, decks/$deckUuid/_deck/sourcing.tsx)
  • 1 uses blue (routes/_menu/auth/login.tsx)
  • deck-odds.tsx and deck-tags-dialog.tsx already use emerald

Acceptance criteria

  • Every Switch in frontend/mtg/src uses color={"emerald"}
  • A Release note fragment, since players see the change
  • Optionally an ast-grep rule in .ast-grep/rules so a new Switch with another colour fails just lint-ast
Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
4h 25m
Merged PRs (30d)
90

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from myOmikron/code

All issues in myOmikron/code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.