Skip to content

Remodel code via Indexed Capability Design Pattern? #90

@JordanMartinez

Description

@JordanMartinez

Due to the concerns raised in #86, I doubt this idea is desired. Still, I thought I would bring it up as a possible discussion.

The idea is to convert this codebase from using a variant of the StateT monad (i.e. Middleware) into using the indexed capability design pattern (see Exploration - Indexed Capability Design Pattern with Indexed Monad Transformers for context).

In my fork of this repo, I'm exploring what this would ultimately look like if the approach was taken, and what are its pain points would be.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions