All issues

prefer-list / no-get-unsafe: two dead options, a code-breaking autofix, and a Wire<T> proposal for boundary-aware List enforcement

#285

· jordanburke opened

on Aug 17, 2026

Tracking: Task → IO consolidation → 2.0

#277

· jordanburke opened

on Aug 3, 2026

Task → IO Phase E: the 2.0 — delete core/task, rename extraction methods

#276

· jordanburke opened

on Aug 3, 2026

Task → IO Phase D: deprecate the Task module

#275

· jordanburke opened

on Aug 3, 2026

Task → IO Phase C: migrate consumers (functype-react + functype-os)

#274

· jordanburke opened

on Aug 3, 2026

Task → IO Phase B: grow IO to absorb Task's unique capabilities

#273

· jordanburke opened

on Aug 3, 2026

IO: no way to propagate external cancellation into a running effect (blocks AbortSignal wiring in functype-react/query)

#242

· jordanburke opened

on Jul 25, 2026

eslint-plugin-functype: recognize interop boundaries structurally (@interop marker) instead of forcing eslint-disable

#241

· jordanburke opened

on Jul 25, 2026

RFC: composable Schedule (retry+repeat policy value) as new functype-schedule package

#220

· jordanburke opened

on Jul 1, 2026

2.0: rename extraction methods to match Scala/Effect (orElse→getOrElse, or→orElse, lazy)

#215

· jordanburke opened

on Jun 22, 2026

CI: track functype core fitness score via functype-eval

#197

· jordanburke opened

on Jun 14, 2026

docs: add `functype/core` curated re-export + cheatsheet mapping Scala/fp-ts names

#141

· jordanburke opened

on May 19, 2026