chore: upgrade to arktype 2

[jhechtf]

TL;DR

Updated arktype to v2.0.4 and improved form validation patterns across authentication flows.

What changed?

• Upgraded arktype from v1.0.27-alpha to v2.0.4
• Added @jhecht/arktype-utils dependency
• Updated email validation pattern from 'email' to 'string.email'
• Enhanced currency validation to enforce uppercase 3-letter codes
• Removed redundant session validation check in bills deletion
• Cleaned up console.log statements in forgot password flow

How to test?

1. Test form submissions in registration, login, and forgot password flows
2. Verify currency inputs only accept 3-letter uppercase codes (e.g., USD, EUR)
3. Confirm email validation works correctly across all forms
4. Test bill deletion still functions properly
5. Verify password requirements remain intact (minimum 8 characters)

Why make this change?

The upgrade to arktype v2.0.4 provides more robust type validation and better pattern matching capabilities. The standardization of email validation patterns and currency format requirements improves data consistency and reduces potential validation errors.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
bill-tracker-mono	❌ Failed (Inspect)			Feb 22, 2025 8:38pm

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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.

Documentation and Community

• 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.

[jhechtf]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat: Test out PostHog #120
• feat(bills): Adds in payment history chart #119
• test(household): Updating e2e tests for new layout on household page #117
• chore: upgrade to arktype 2 #116 👈 (View in Graphite)
• refactor(households): Redoing some of the layout for the households page #115
• feat(Households): Adds in a quick-and-dirty workflow for ownerless households #114
• feat: Add in Alert component,No tests as it's almost entirely a display-based component #113
• test: Add in dropzone stories #112
• test: Adds Drawer unit tests #111
• test(Button): Adds extra stories and a minor unit test #110
• test: Add in unit test setup #109
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.