Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add a Cron Expression Explainer tool

Aperta
  • Qualcosa non va?
#86 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
58/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
nextjs, tailwindcss, typescript
Ambito
developer-experience, frontend

Direzione di ricerca

Read lib/tools.ts and its Tool interface, then inspect the complete example in app/(tools)/base64/ and the Add a tool section of the README. Implement the pure cron logic in lib/cron.ts with tests in lib/__tests__/cron.test.ts, then add the registry entry and route, client, and Open Graph image. Done means the listed acceptance tests, scoped UI, checklist, and lint, test, and build commands all pass.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement hacktoberfest help wanted new tool

Paste a crontab line and get a plain-English description plus the next run times. It's useful any time you touch CI schedules, Kubernetes CronJobs or GitHub Actions.

Route: /cron-explainer

Suggested registry values: title Cron Expression Explainer, tagline Scheduling, heroHeading Cron Expression Explainer with heroDim "", features ["Plain English", "Next runs", "Ranges and steps", "Macros", "UTC or local"].

Core logic in lib/cron.ts (no new dependency, please)

  • parseCron(expr) for standard 5-field cron (minute, hour, day of month, month, day of week) with *, lists, ranges, steps (*/15, 1-10/2), names (JAN, MON) and macros (@hourly, @daily, @weekly, @monthly, @yearly). Errors name the field that failed.
  • describeCron(parsed) returning an English sentence
  • nextRuns(parsed, from: Date, count, { utc }) returning Date[]. Follow the classic rule that when both day of month and day of week are restricted, a time matches if either one matches. Cap the search horizon so an impossible schedule like 0 0 31 2 * returns an empty list with a message instead of looping.

v1 scope: the input, the description, a field-by-field breakdown table, the next 5 runs with a UTC / local toggle, and a few preset chips.

Out of scope for v1: seconds and year fields (Quartz style), Jenkins H syntax, a timezone picker.

Where to look

  • lib/tools.ts (the registry and the Tool interface)
  • app/(tools)/base64/ (a complete tool to copy the structure from)
  • The "Add a tool" section of the README

Acceptance criteria

  • Tests: */15 * * * * is described as every 15 minutes, 0 9 * * 1-5 as weekdays at 09:00, nextRuns from a fixed UTC date, the day-of-month or day-of-week rule (0 0 1 * 1), 0 0 31 2 * returns no runs, and 60 * * * * errors and mentions the minute field
  • UI as scoped above
  • The standard new-tool checklist below is complete

Standard new-tool checklist

Everything (home grid, metadata, JSON-LD, OG image, sitemap, manifest, command palette) is driven by the registry in lib/tools.ts, so a new tool is mostly one registry entry plus a route.

  • Add an entry to TOOLS in lib/tools.ts filling every field of the Tool interface (lib/tools.ts:19-52). Use applicationCategory: "DeveloperApplication", reuse the CTA_PROJECTS / CTA_CONTACT constants for the CTA links, and set sitemapPriority: 0.9 like the other tools.
  • Pick accentVar from the accent variables in app/globals.css (the list is under "Adding a tool" in CONTRIBUTING.md). Take one that no tool uses yet, or the one the fewest tools have if they're all taken. Don't use --rose, it's the color of error messages. Set accentHex to that variable's dark-theme value. heroDim must be "" or a substring of heroHeading.
  • Write 3 or 4 FAQs (3 renders as a 3-column grid, see components/shared/ToolPageLayout.tsx:25). Keep metaTitle under 60 characters and metaDescription around 150 to 160.
  • Keep features and ogDescription to plain Latin text and punctuation. The social card font is a subset with no arrow or symbol glyphs (lib/og.tsx:33-36).
  • Create app/(tools)/<slug>/page.tsx, <Name>Client.tsx (with "use client"), and opengraph-image.tsx. Copy page.tsx and opengraph-image.tsx from app/(tools)/base64/ and change the slug.
  • Put all pure logic in lib/<name>.ts (no React, no DOM) with tests in lib/__tests__/<name>.test.ts. Tests can import with @/ like the app does (vitest.config.ts has the alias).
  • Nothing leaves the browser: no network calls with user input, no analytics, no third-party scripts (the CSP in middleware.ts blocks external scripts anyway).
  • Reuse shared pieces: CopyButton, useToast, and optionally useRegisterCommands for command palette actions (example in app/(tools)/base64/Base64Client.tsx:43-53).
  • Every input has a visible label or an aria-label, the tool works with the keyboard alone, and it looks right in both light and dark themes.
  • Add the tool to the "Which tool?" dropdown in .github/ISSUE_TEMPLATE/bug_report.yml.
  • npm run lint && npm run test && npm run build passes.

One new tool per contributor, so more people get a chance. Add your registry entry at the end of TOOLS and rebase on develop before asking for review, since other new tools will touch the same file.

Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off develop, and open your PR against develop with Closes #86 in the description.

Lingua principale
TypeScript
Stelle
1
Fork
9
Merge medio
9h 50m
PR unite (30g)
105

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di codercops/toolbelt

Tutte le issue di codercops/toolbelt

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.