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.

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

move to stack with lts-8.19 #42

Merged
merged 4 commits into from
Jul 2, 2017
Merged

Conversation

chadselph
Copy link

I don't actually know what I'm doing, but I got this to compile.

I can't run the tests because they only work on your account.

@markandrus
Copy link
Owner

markandrus commented Jun 22, 2017 via email

throwForNon204 _ resp =
case responseStatus resp of
Status 204 _ -> return ()
status -> do
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since status is unused, why not

    Status 204 _ -> return ()
    _ -> do

Also, we may want to prefer pure to return, but it's a minor thing. Better to catch with some kind of style-check in the future...

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't know the difference between pure and return. I actually had pure first, I can change it back.

twilio.cabal Outdated
http-client-tls,
network-uri,
text,
transformers,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know much about Stack, but in order for this package to continue working with vanilla Cabal/Hackage, don't we need to keep some known version bounds in the .cabal file?

Copy link
Author

@chadselph chadselph Jun 28, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I don't know either.

my understanding is stack will generate the .cabal file with the specific versions (found in the build-plan: lts-8.19)

@markandrus
Copy link
Owner

Thanks, @chadselph. I had one comment and one question, namely: will this continue working with vanilla Cabal/Hackage?

I can't run the tests because they only work on your account.

Right, Travis keeps the credentials private on PRs from forks. Any thoughts on how to improve the tests? #31 is one path forward for unit tests, and then integration tests (requiring credentials) could perhaps be optional.

@chadselph
Copy link
Author

#31 seems good, I was kind of surprised it wasn't already working this way. But is it possible to make that change backwards compatibly?

@eriknstevenson
Copy link
Contributor

Thanks @chadselph for making these updates. I was just about to make them myself, but was glad to see someone had beat me to it. I opened a PR on your fork to re-add the package bounds in the cabal file.

@markandrus
Copy link
Owner

Thanks @chadselph @Narrative I'll try this out now. I think we'll probably want to update the .travis.yml to test the stack path in addition to cabal.

@markandrus markandrus merged commit 23ff41a into markandrus:master Jul 2, 2017
@markandrus markandrus mentioned this pull request Oct 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants