Feature request · API & developer experience · Blocks work
Make the abuse library immutable
1 source thread · first seen 2026-10
Every GitHub thread behind this item is closed (latest 2026-10). The problem may be fixed in current versions; check the source threads below before relying on it.
Summary
The request proposes replacing mutable abuse adapters with immutable classes and value objects. It cites stale cached counts and timestamps, state changes during getters, and inconsistent adapter methods as problems with the current design.
- Affects
- Developers using the abuse library
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Refactor it to the immutable style already used across `packages/`: `final readonly` classes with promoted constructor properties, `with*()` methods that return a clone, and value”