Add Upgrade guide from 1.0.0 to 2.0.0 #49

Activity

1. evancz commented on Nov 20, 2018

   

   evancz

   on Nov 20, 2018

   Member

   More actions

   What are you running into? What sort of things do you think it'd be best to document?
2. deiga commented on Nov 21, 2018

   

   deiga

   on Nov 21, 2018

   Author

   More actions

   @evancz The changed type signature for all requests was the biggest hurdle I encountered when I tried to do the upgrade.
   As well as small things like parameters changing in the custom requests.

   I didn't put much effort into it yet, but these felt so big that I just couldn't handle the upgrade right now :P

   👍React with 👍1Reacted by Istvan
3. bryce13950 commented on Dec 17, 2018

   

   bryce13950

   on Dec 17, 2018

   More actions

   A quick guide on how the types have changed would be great. A simple document that shows 1.0.0 implementation, and then the same implementation in 2.0.0 would probably suffice.
4. christelnagels commented on Mar 6, 2019

   

   christelnagels

   on Mar 6, 2019

   Last edited by christelnagels

   More actions

   My friend @Hermanverschooten made a post on elm-discourse describing how he upgraded my code to 2.0,
5. michaelglass commented on Jul 15, 2019

   

   michaelglass

   on Jul 15, 2019

   Last edited by michaelglass

   More actions

   We just made a shim between 1.0 and 2.0 to help people upgrade from 1.0 to 2.0: https://github.com/NoRedInk/http-upgrade-shim

   It provides an, albeit awkward, step-by-step approach to upgrading elm/http.

   🎉React with 🎉1Reacted by Bryce Meyer