Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Changing timeouts is too difficult #100

Closed
i-am-the-slime opened this issue Aug 20, 2019 · 1 comment · Fixed by #101
Closed

Changing timeouts is too difficult #100

i-am-the-slime opened this issue Aug 20, 2019 · 1 comment · Fixed by #101

Comments

@i-am-the-slime
Copy link
Member

What should be a pretty straightforward use case becomes pretty crazy (and ugly)

main ∷ Effect Unit
main = do
  specs <- discover "\\.*Spec"
  runSpecT config [ consoleReporter ] specs # un Identity # launchAff_
  where
  config =
    defaultConfig
      { slow = 5.0 # Seconds # fromDuration
      , timeout = Nothing
      }

How about runSpecWithConfig in a way that the un Identity can be avoided?
@safareli safareli mentioned this issue Aug 22, 2019
Merged
@safareli
Copy link
Member

https://github.com/purescript-spec/purescript-spec/releases/tag/v4.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add runSpec' purescript-spec/purescript-spec
2 participants
@i-am-the-slime @safareli