elm-explorations / elm-explorations/test

Reintroduce `Expect.true/false` with a better API?

Open
#224 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Elm
Stars
244
Forks
40
Avg merge
1d 23h
Merged PRs (30d)
2

Description

Maybe we should make it easier to do this:
```elm
|> Expect.equal True
|> Expect.onFail "The URL should still be present in the final URL after running autolinksUrl"
```
by having something like
```elm
|> Expect.true { onFalse = "The URL ..." }
```

The previous maintainers' reasons for removing `Expect.true` was that it took away the spotlight from better solutions (`Expect.equalLists`, ...), but sometimes you just have to work with predicates. It's not always possible/practical to use the other helpers. Let's trust our users to understand when to use which solution?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.