Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/noredink/http-upgrade-shim
https://github.com/noredink/http-upgrade-shim
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/noredink/http-upgrade-shim
- Owner: NoRedInk
- License: bsd-3-clause
- Created: 2019-07-04T13:28:43.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2019-07-04T13:46:07.000Z (over 5 years ago)
- Last Synced: 2024-05-08T23:24:40.435Z (8 months ago)
- Language: Elm
- Homepage:
- Size: 14.6 KB
- Stars: 2
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# NoRedInk/http-upgrade-shim
## Helping you gradually upgrade your application to the elm/http 2.0 API!
The APIs between elm/http 1.0 and 2.0 changed a lot. This shim consumes elm/http 2.0 and exposes an API that's mostly compatible with elm/http 1.0
## Upgrading elm/http from 1.0 to 2.0
1. Use [elm-json](https://github.com/zwilias/elm-json) to find out if any packages are preventing you from upgrading.
```
$ elm-json install elm/[email protected]
-- NO VALID PACKAGE VERSIONS FOUND ---------------------------------------------
Because NoRedInk/elm-string-conversions 1.0.0 depends on elm/http
1.0.0 <= v < 2.0.0 and this project depends on elm/http 2.0.0,
NoRedInk/elm-string-conversions 1.0.0 is incompatible with this project.
And because this project depends on NoRedInk/elm-string-conversions 1.0.0,
no valid set of package versions could be found.
```
2. Copy the source code of any of those packages directly into your codebase, and, remove the packages from your `elm.json`
3. Upgrade to elm/http 2.0 `elm install elm/http`
4. In your code base as well as the packages copied over, replace `import Http` with `import Http.Legacy as Http`
5. Done!
## Limitations
- This doesn't support `Http.Progress`
- This hasn't been tested
---
[](http://noredink.com/about/team)