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

Made-up Event files for both Regions

Open
  • Is something wrong?
#53 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend, testing

Research direction

Read docs/specs/regions-events-and-sandbox.md on branch 21-grill-regions and inspect the real Event schema, build packing, and Event picker. Check the blocker #48 before starting. Add schema validation with bad-field errors, then implement the two regional examples and tests; done means the listed acceptance criteria pass, including scripts/check.sh and updates to affected glossary, docs, and lessons.

Written by the indexing model from the issue text.

Description

area: node feature ready-for-agent

Parent

#26

What to build

A Region author can hand-write a made-up Event in regions/<name>/events/ to test the network on a flood that never happened. Its weather is a few hand-written keyframes applied evenly. The build checks it against the Event schema, naming the bad field, and packs it in the same shape as a real Event. Fort Myers and Nepal each ship one.

Spec

docs/specs/regions-events-and-sandbox.md

Acceptance criteria

  • An Event schema shared by real and made-up Events; the build names the bad field
  • One made-up Event each for Fort Myers (storm surge) and Nepal (flash flood), playable from the Event picker and marked as not real
  • Build test: a made-up Event's keyframes become its weather in the pack
  • Tests that need a calm coast Event can use the made-up one instead of Ian
  • scripts/check.sh passes; glossary entries, docs and lessons lines this change makes untrue are fixed in the same PR

Blocked by

  • #48
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
56m
Merged PRs (30d)
42

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 StormShields/Stormshield

All issues in StormShields/Stormshield

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.