https://github.com/lenards/elm-http-pipeline

A library for building HTTP requests using the pipeline (`|>`) operation and plain function calls.
https://github.com/lenards/elm-http-pipeline

Last synced: about 2 months ago
JSON representation

A library for building HTTP requests using the pipeline (`|>`) operation and plain function calls.

• Host: GitHub
• URL: https://github.com/lenards/elm-http-pipeline
• Owner: lenards
• License: mit
• Created: 2019-08-31T22:33:04.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2022-12-10T00:38:45.000Z (about 2 years ago)
• Last Synced: 2024-04-11T15:19:57.810Z (9 months ago)
• Language: Elm
• Size: 211 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# elm-http-pipeline

A library for building HTTP requests using the pipeline (`|>`) operation and plain function calls.

## Context

I enjoy using `Json.Decode.Pipeline` and when looking at Alex Korban's ["How JSON Decode Pipeline Chaining Works"](https://korban.net/posts/elm/2018-07-10-how-json-decode-pipeline-chaining-works/?__s=4wkzui9hudcqgabdzvw2). In seeing how the `required` and `optional` function work, I was curious if I might be able to do that for another "records" (aka `type alias Blah`).

I am not sure what I am doing here is a _good_ idea (**at all**). In other words, "here _might_ be **slow** monsters".

## Testing

I am hoping to put this to use in testing the requests created:

- https://package.elm-lang.org/packages/avh4/elm-program-test/3.0.0/