Closed danstn closed 7 years ago
Should probably use a specific version of Node instead (example travis setup).
Great. I'll take a look tonight after work. 👍 for using elm-css as a guide.
Additionally, what are your thoughts on this travis setup: https://github.com/krisajenkins/remotedata
I'd be happy to not introduce node-test-runner
if we don't have to. I suppose it's not that big of a deal though.
I'll keep playing with this though and let you know what I think.
That exactly where I started: https://github.com/john-kelly/elm-postgrest/pull/5/commits/534f04341c2b341838c466fa1a3c5dabdc067a87
Test runner blows up on Promise
s (cause of node version I think).
See this failing build.
Not really sure what's the best way to go about it. elm-test
worked fine for me in the past so I just went for it.
I looked at a few more examples and it looks like you implemented the "best practice" test suite. I think this is good to go 👍
This PR Build Status:
... and a "self-documenting" Makefile:
For #4.