fix: evoting timezone issue

[coodos]

Description of change

Issue Number

Type of change

• Breaking (any change that would cause existing functionality to not work as expected)
• New (a change which implements a new feature)
• Update (a change which updates existing functionality)
• Fix (a change which fixes an issue)
• Docs (changes to the documentation)
• Chore (refactoring, build scripts or anything else that isn't user-facing)

How the change has been tested

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• New Features

  • Deadlines entered in local time are automatically converted to UTC during poll creation.
  • A confirmation toast displays the entered local time alongside its UTC equivalent after submission.

• Documentation

  • Deadline helper text updated to note automatic UTC conversion.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Implements client-side conversion of a user-entered local deadline to a UTC ISO string before invoking createPoll. Updates the API payload to use the UTC value, adds console logging and a toast showing the conversion, and expands the deadline helper text to note automatic UTC conversion.

Changes

Cohort / File(s)	Summary
Deadline UTC conversion & payload update platforms/eVoting/src/app/(app)/create/page.tsx	Added local-to-UTC conversion in onSubmit; API payload now uses deadline: utcDeadline. Logged conversion details and displayed a toast. Extended deadline helper text to mention automatic UTC conversion. No exported/public API changes.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor U as User
  participant P as Create Poll Page
  participant T as Toast/Console
  participant A as createPoll API
  participant B as Backend

  U->>P: Submit form (deadline: local datetime)
  P->>P: Convert local datetime -> UTC ISO (utcDeadline)
  P-->>T: Show toast + log conversion
  P->>A: createPoll({ ..., deadline: utcDeadline })
  A->>B: POST /polls with UTC deadline
  B-->>A: Response
  A-->>P: Result
  P-->>U: Success/Failure feedback

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A bunny taps the submit key,
Turns local ticks to UTC.
A toast pops up, “see time made right,”
Logs glow softly in the night.
Payloads hop to backend’s den—
Deadlines aligned, we’re on time again. 🐇⏰

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 9226fe0 and 6cb4b03.

📒 Files selected for processing (1)

• platforms/eVoting/src/app/(app)/create/page.tsx (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/time-zone-issue-evoting

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.