fix: rename "everySenconds" to "everySeconds"

[armfuldev]

fixes a typo, docs correctly reference everySeconds while the package has a typo.

Summary by CodeRabbit

• Refactor
  • Renamed a public scheduling method from everySenconds to everySeconds to correct a typo. Behavior remains the same (defaults to 1 second and returns the same schedule pattern).
  • The exposed property name on the public Patterns API now reflects the corrected spelling.
  • Action required: update any references in your code from everySenconds to everySeconds to avoid runtime errors.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Renamed a function in src/schedule.ts: FunctionExpressions.everySenconds → FunctionExpressions.everySeconds. The implementation and default parameter (seconds = 1) are unchanged. This alters the public API name exposed via the exported Patterns object.

Changes

Cohort / File(s)	Summary
Schedule API rename src/schedule.ts	Renamed FunctionExpressions method everySenconds to everySeconds; same implementation and default argument. Publicly changes the corresponding property on the exported Patterns object.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

I twitch my whiskers, tap-tap—rename complete!
A missing vowel fixed; now seconds skip in beat.
From senconds to seconds, neat and clean,
Our cron now speaks the name it means.
I thump in joy—ship it fleet! 🐇⏱️

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 105aeeb and ee02f72.

📒 Files selected for processing (1)

• src/schedule.ts (1 hunks)

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[armfuldev]

seems to be a duplicate of #53, closing