Skip to content

unfortunate interaction with ghcid #43

Open

Description

@mwotton

When I run with ghcid -T :main -c "cabal repl tests" and add or remove a test in a module used by the generated tasty-discover test module, ghcid doesn't get a trigger to actually reload the top level module, so new tests don't get run, and removed (or renamed) tests get an error that the previous name was not found. I recognise this isn't really tasty-discover's fault, it's a knock-on effect of the way ghcid loads files, but is there a workaround? I tried the --in-place` option, but it just sends ghcid into a reload loop.

Activity

  1. newhoggy commented on Aug 10, 2025

    @newhoggy
    Member

    Does this solve your problem?

    #75

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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