PureScript Open Rows for Type-Safe Record Enrichment
Use PureScript open row polymorphism to require specific record fields while preserving unknown fields through transformations, checked at compile time.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use PureScript open row polymorphism to require specific record fields while preserving unknown fields through transformations, checked at compile time.
PureScript row polymorphism allows for type-safe configuration merging. Learn how to use row constraints and Record.merge to ensure required keys exist at compile time.
An architecture note describing how to use PureScript’s FFI to call JavaScript safely, covering requirements, minimal design, trust boundaries, checks, failure modes, and when to redesign.
Decide when to use raw PureScript FFI versus purescript-foreign boundary decoding for safer JavaScript interop.
PureScript's FFI lets you call JavaScript, but the compiler cannot see runtime shapes. Here is how to choose between direct bindings and purescript-foreign decoding.
Row polymorphism lets PureScript functions accept records with extra fields while keeping static type safety. Learn the syntax, a worked example, and the limits.
Decide which PureScript FFI style to use when calling JavaScript, with a comparison table, trade-offs, and a validated spago workflow.
Learn how to expose JavaScript functions to PureScript using the Foreign Function Interface (FFI). Follow a step‑by‑step guide with a Lodash example, setup details, and trade‑off discussion.
Learn how to use PureScript's row polymorphism to create extensible record types, ensuring data pipelines preserve extra fields while maintaining strict compile-time type safety.