Skip to content

Comments

fix: Fix digest scheduling optional param#791

Merged
elie222 merged 1 commit intoelie222:mainfrom
edulelis:fix-digest-schedule-typing
Sep 16, 2025
Merged

fix: Fix digest scheduling optional param#791
elie222 merged 1 commit intoelie222:mainfrom
edulelis:fix-digest-schedule-typing

Conversation

@edulelis
Copy link
Collaborator

@edulelis edulelis commented Sep 16, 2025

Summary by CodeRabbit

  • Refactor
    • Improved scheduling input flexibility to gracefully handle missing previous occurrence data, with no change to current behavior.
  • Chores
    • Internal type-safety updates to enhance robustness. No user-facing changes.

@vercel
Copy link

vercel bot commented Sep 16, 2025

@edulelis is attempting to deploy a commit to the Inbox Zero OSS Program Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 16, 2025

Walkthrough

Updated the TypeScript type for the calculateNextScheduleDate function’s frequency parameter in apps/web/utils/schedule.ts, making lastOccurrenceAt optional via Partial. No runtime logic or control flow changes were made; destructuring still reads lastOccurrenceAt, and scheduling behavior remains the same.

Changes

Cohort / File(s) Summary
Schedule utils typing update
apps/web/utils/schedule.ts
Adjusted function signature: frequency now is Pick<Schedule, "intervalDays" | "daysOfWeek" | "timeOfDay" | "occurrences"> & Partial<Pick<Schedule, "lastOccurrenceAt">>. Runtime logic unchanged; lastOccurrenceAt may be undefined and is handled as before.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

Poem

A tick of time, a hop ahead,
I nibble types where schedules tread.
Last seen? Perhaps—perhaps not there,
Optional whiskers in TypeScript air.
Dates align, no routes askew—
Thump-thump! The calendar knows what to do. 🐇⌚️

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "fix: Fix digest scheduling optional param" accurately reflects the main change in the diff: a type-level update making lastOccurrenceAt optional for calculateNextScheduleDate in apps/web/utils/schedule.ts, so it is on-topic and concise; it does include a redundant "Fix" after the conventional "fix:" prefix but remains clear about the intent.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
✨ Finishing touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
apps/web/utils/schedule.ts (2)

114-123: Update JSDoc to reflect param rename and optionality

Docs still reference schedule.* and imply lastOccurrenceAt is required. Align with the new signature.

- * @param schedule - The schedule configuration
- * @param schedule.daysOfWeek - Bitmask of days of the week (see DAYS constant)
- * @param schedule.intervalDays - Number of days between occurrences
- * @param schedule.timeOfDay - Time of day for the occurrence (if unset, defaults to midnight)
- * @param schedule.occurrences - Number of occurrences within the interval
- * @param schedule.lastOccurrenceAt - The last occurrence time (used as reference point)
+ * @param frequency - The schedule configuration
+ * @param frequency.daysOfWeek - Bitmask of days of the week (see DAYS constant)
+ * @param frequency.intervalDays - Number of days between occurrences
+ * @param frequency.timeOfDay - Time of day for the occurrence (if unset, defaults to midnight)
+ * @param frequency.occurrences - Number of occurrences within the interval
+ * @param frequency.lastOccurrenceAt - Optional last occurrence time (used as reference point)

155-167: Fractional slots are currently truncated by date-fns addDays; use milliseconds to preserve spacing

date-fns addDays truncates decimals, so slotLength fractions are lost. This yields incorrect intra-interval spacing when occurrences > 1.

-    // Find the next slot
+    // Find the next slot
     for (let i = 0; i < occ; i++) {
-      // Calculate slot offset in days (preserves fractional spacing)
-      const dayOffset = i * slotLength;
-      const slotDate = addDays(intervalStart, dayOffset);
+      // Calculate slot offset in days (preserve fractional spacing)
+      const dayOffset = i * slotLength;
+      const slotDate = new Date(intervalStart.getTime() + dayOffset * 86_400_000);
       setTime(slotDate);

No change needed for nextIntervalStart; it’s an integer-day jump.

Also applies to: 174-176

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fe2992b and 37a19b6.

📒 Files selected for processing (1)
  • apps/web/utils/schedule.ts (1 hunks)
🧰 Additional context used
📓 Path-based instructions (8)
apps/web/**/*.{ts,tsx}

📄 CodeRabbit inference engine (apps/web/CLAUDE.md)

apps/web/**/*.{ts,tsx}: Use TypeScript with strict null checks
Path aliases: Use @/ for imports from project root
Use proper error handling with try/catch blocks
Format code with Prettier
Leverage TypeScript inference for better DX

Files:

  • apps/web/utils/schedule.ts
!{.cursor/rules/*.mdc}

📄 CodeRabbit inference engine (.cursor/rules/cursor-rules.mdc)

Never place rule files in the project root, in subdirectories outside .cursor/rules, or in any other location

Files:

  • apps/web/utils/schedule.ts
**/*.ts

📄 CodeRabbit inference engine (.cursor/rules/form-handling.mdc)

**/*.ts: The same validation should be done in the server action too
Define validation schemas using Zod

Files:

  • apps/web/utils/schedule.ts
**/*.{ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/logging.mdc)

**/*.{ts,tsx}: Use createScopedLogger for logging in backend TypeScript files
Typically add the logger initialization at the top of the file when using createScopedLogger
Only use .with() on a logger instance within a specific function, not for a global logger

Import Prisma in the project using import prisma from "@/utils/prisma";

**/*.{ts,tsx}: Don't use TypeScript enums.
Don't use TypeScript const enum.
Don't use the TypeScript directive @ts-ignore.
Don't use primitive type aliases or misleading types.
Don't use empty type parameters in type aliases and interfaces.
Don't use any or unknown as type constraints.
Don't use implicit any type on variable declarations.
Don't let variables evolve into any type through reassignments.
Don't use non-null assertions with the ! postfix operator.
Don't misuse the non-null assertion operator (!) in TypeScript files.
Don't use user-defined types.
Use as const instead of literal types and type annotations.
Use export type for types.
Use import type for types.
Don't declare empty interfaces.
Don't merge interfaces and classes unsafely.
Don't use overload signatures that aren't next to each other.
Use the namespace keyword instead of the module keyword to declare TypeScript namespaces.
Don't use TypeScript namespaces.
Don't export imported variables.
Don't add type annotations to variables, parameters, and class properties that are initialized with literal expressions.
Don't use parameter properties in class constructors.
Use either T[] or Array consistently.
Initialize each enum member value explicitly.
Make sure all enum members are literal values.

Files:

  • apps/web/utils/schedule.ts
apps/web/utils/**

📄 CodeRabbit inference engine (.cursor/rules/project-structure.mdc)

Create utility functions in utils/ folder for reusable logic

Files:

  • apps/web/utils/schedule.ts
apps/web/utils/**/*.ts

📄 CodeRabbit inference engine (.cursor/rules/project-structure.mdc)

apps/web/utils/**/*.ts: Use lodash utilities for common operations (arrays, objects, strings)
Import specific lodash functions to minimize bundle size

Files:

  • apps/web/utils/schedule.ts
**/*.{js,jsx,ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)

**/*.{js,jsx,ts,tsx}: Don't use elements in Next.js projects.
Don't use elements in Next.js projects.
Don't use namespace imports.
Don't access namespace imports dynamically.
Don't use global eval().
Don't use console.
Don't use debugger.
Don't use var.
Don't use with statements in non-strict contexts.
Don't use the arguments object.
Don't use consecutive spaces in regular expression literals.
Don't use the comma operator.
Don't use unnecessary boolean casts.
Don't use unnecessary callbacks with flatMap.
Use for...of statements instead of Array.forEach.
Don't create classes that only have static members (like a static namespace).
Don't use this and super in static contexts.
Don't use unnecessary catch clauses.
Don't use unnecessary constructors.
Don't use unnecessary continue statements.
Don't export empty modules that don't change anything.
Don't use unnecessary escape sequences in regular expression literals.
Don't use unnecessary labels.
Don't use unnecessary nested block statements.
Don't rename imports, exports, and destructured assignments to the same name.
Don't use unnecessary string or template literal concatenation.
Don't use String.raw in template literals when there are no escape sequences.
Don't use useless case statements in switch statements.
Don't use ternary operators when simpler alternatives exist.
Don't use useless this aliasing.
Don't initialize variables to undefined.
Don't use the void operators (they're not familiar).
Use arrow functions instead of function expressions.
Use Date.now() to get milliseconds since the Unix Epoch.
Use .flatMap() instead of map().flat() when possible.
Use literal property access instead of computed property access.
Don't use parseInt() or Number.parseInt() when binary, octal, or hexadecimal literals work.
Use concise optional chaining instead of chained logical expressions.
Use regular expression literals instead of the RegExp constructor when possible.
Don't use number literal object member names th...

Files:

  • apps/web/utils/schedule.ts
!pages/_document.{js,jsx,ts,tsx}

📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)

!pages/_document.{js,jsx,ts,tsx}: Don't import next/document outside of pages/_document.jsx in Next.js projects.
Don't import next/document outside of pages/_document.jsx in Next.js projects.

Files:

  • apps/web/utils/schedule.ts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: cubic · AI code reviewer
🔇 Additional comments (1)
apps/web/utils/schedule.ts (1)

127-130: Type change to make lastOccurrenceAt optional — LGTM

rg shows calculateNextScheduleDate callsites in tests (apps/web/utils/schedule.test.ts) and runtime code (apps/web/utils/actions/settings.ts, apps/web/app/api/resend/digest/route.ts); callers either pass lastOccurrenceAt or intentionally omit/null it. Run a full TypeScript type-check (tsc --noEmit or CI) to confirm all callsites type-check.

Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@elie222 elie222 merged commit 5c415a2 into elie222:main Sep 16, 2025
9 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants