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

Upgrade to elm/http 2.0.0 #23

Closed
Natim opened this issue Nov 15, 2018 · 8 comments
Closed

Upgrade to elm/http 2.0.0 #23

Natim opened this issue Nov 15, 2018 · 8 comments

Comments

@Natim
Copy link

Natim commented Nov 15, 2018

No description provided.

@lukewestby
Copy link
Owner

hey @Natim, sorry this is holding up your upgrade for the kinto client. i'm still working out how the api will change. if you have input i'd be happy to hear it

@Natim
Copy link
Author

Natim commented Dec 13, 2018

Don't worry too much about it :) I will ping @magopian and @n1k0 who might have insights too.

@Natim
Copy link
Author

Natim commented Dec 13, 2018

To be honest I really like the way it currently is 😂

dvekeman added a commit to dvekeman/elm-http-builder that referenced this issue Jan 15, 2019
@absynce
Copy link

absynce commented Mar 23, 2019

Is the API discussion for this going on anywhere? I imagine this upgrade will have some important implications on the API.

Motivation: I'm looking into upgrading a client project to elm/http 2.0.0.

@kornicameister
Copy link

kornicameister commented Apr 10, 2019

Same motivation. I find default API of elm/http somehow crude. Have been using this library always with elm/http<2.0.0 and it as convenient as elm-json-pipeline. If there's some help needed, perhaps I can help.

@lukewestby
Copy link
Owner

Hey folks, I would actually love a PR for this. I’ve been overloaded recently with personal stuff and getting the elm-conf cfp started. If you want any kind of guidance just @ me in a review comment

@kornicameister
Copy link

@lukewestby there is a PR already #25 :)

@lukewestby
Copy link
Owner

alright folks, this is done. sorry for the wait. i'm gonna find someone to take over maintaining this package so it doesn't happen again

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

No branches or pull requests

4 participants