Building Web Applications with Signals at Grammarly
summary
Signals replace tangled useState logic with a view model class of Grammarly/ficalal atoms that act like synchronous values and observable streams, wired into React via a small hook. Implementation uses rxgs behavior‑subjects under the hood, buffering/throttling edits, sending diffs for long documents, and decoupling UI from business logic. Tests include synchronous unit checks plus time‑based marble tests and property testing for diffs; the system runs in production with explicit dispose/unsubscribe paths.
AI-written summary · about
chapters (11)
- 0:00Introduction to Signals in Grammarly
- 3:06Understanding Signals and Their Usage
- 5:51Integrating Signals in React
- 9:08Benefits of Using Signals in React
- 10:12Testing and Value Over Time in Signals
- 13:00Testing with Marble Tests
- 15:19Working with Signals in Grammarly
- 18:41Handling Cleanup and Unsubscribing to Signals
- 21:41Challenges in Signal-Driven Systems
- 24:36Marble Tests and Combined States
- 27:41Signals Proposal and Migration
related talks
06mEmbracing Reactivity: Signals Unveiled in Modern Web Frameworks
52mIt's Time To Talk About Signals
31mAre Signals Worth the Hype?
47mMastering Complex UI: State Machines and Reactive Patterns
19mAngular Signals: A Look Under the Hood and Beyond
30mAre Signals worth the hype?
48mJS Signals
28mSignals: What, How, and Why!