Cole Lawrence

@colelawrence.com

540 Followers 568 Following

End user programming & AI tool designer. 🛠️ CTO at https://phosphor.co & @forethink.ai 🦀 Rust NYC / https://RustEastCoast.com organizer 🙋🏻‍♂️he/him

Shows how the same TODO markdown file is synchronized in the "floating tracker view", "planner view", and the editor

Screenshot of Windsurf's Cascade window (AI writing chat)
---
Edited
memoize.ts
+4
-4
78
Open diff
The key change is that we now cache the Promise itself rather than waiting for its resolution. This ensures that concurrent calls will get the same Promise instance, and thus the function will only be called once.

Let's run the tests again:

Ran terminal command
application/ui
$ pnpm vitest run memoize

Stdout
CopyInsert

RUN v2.1.3 /Users/cole/dev/forethink-web-extension/application/ui

✓ src/core_application/js/__tests__/memoize.test.ts (7 tests) 4ms

Test Files 1 passed (1)
Tests 7 passed (7)
Start at 16:20:41
Duration 707ms (transform 80ms, setup 119ms, collect 17ms, tests 4ms, environment 189ms, prepare 76ms)

Great! All tests are now passing. Here's a summary of what we've done:

Created comprehensive tests for both memoize and memoizeWithExpiration functions
Fixed the concurrent calls handling in memoizeWithExpiration by:
Caching the Promise instead of its resolved value
Using ExpiryCache to handle expiration timing
Properly handled time-based tests using Vitest's fake timers
The test suite now verifies:

Basic caching functionality
Expiration timing
Custom key functions
Zero expiration cases
Concurrent calls
All functionality is working as expected, with proper handling of async operations and cache expiration.

Your modified files:
memoize.ts
application/ui/src/core_application/js
+3
-3
Me: Update tests to handle null expiration time on set

Windsurf for macOS after fixing a bug with "Cascade" mode