Memoization / caching of cipher computations

[Aditya8369]

Summary of Changes
lib/hooks/useCipherWorker.ts:

Persistent cache: Introduced a module-level resultCache Map which retains results across component cycles, unmounts, and worker thread recreations.
LRU cache eviction policy: Enforced a MAX_CACHE_SIZE = 200 limit. When reached, it automatically evicts the oldest items to avoid memory leaks.
Stable sorting keys: Added sortObjectKeys helper to recursively sort keys of options, ensuring that identical parameters are matched correctly regardless of property definition ordering.
Cache bypassing: Supports a bypassCache?: boolean option inside options to force computations to run on the Web Worker thread (essential for testing or raw benchmarks).
Cache reset: Exposed a clearCipherWorkerCache() utility for isolated test setup.
tests/unit/hooks/useCipherWorker.test.ts:

Added unit tests for memoization (ensuring repeated worker execution is bypassed), the bypassCache option, and the LRU boundary constraint/eviction mechanism. All tests compile and pass successfully.

closes #83

[vercel]

@Aditya8369 is attempting to deploy a commit to the csxark's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Warning

Review limit reached

@Aditya8369, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 63a09e87-fc35-46b5-bef6-215db736fe07

📥 Commits

Reviewing files that changed from the base of the PR and between 245e776 and 0feea00.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• components/cipher/CipherLayout.tsx
• lib/hooks/useCipherWorker.ts
• lib/workers/cipher.worker.ts
• tests/unit/hooks/useCipherWorker.test.ts
• types/worker.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[csxark]

Great work @Aditya8369, and thank you for your contribution! 🎉I've reviewed the changes, and everything looks good. The requested fixes have been addressed correctly, and the implementation aligns well with the requirements. This is ready to be merged. Looking forward to your future contributions!