Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upadd uriEncode and uriDecode #702
Conversation
added some commits
Aug 28, 2016
lukewestby
added
the
request
label
Aug 28, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
process-bot
Aug 28, 2016
Thanks for the pull request! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
process-bot
commented
Aug 28, 2016
|
Thanks for the pull request! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
Aug 29, 2016
Member
These exist evancz/http like this.
I think a better move would be to move Http into core, and it is on my todo list, but I'd like to get 0.18 out before doing something like that.
|
These exist I think a better move would be to move |
evancz
closed this
Aug 29, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
|
evancz
deleted the
luke/uri_encode_decode
branch
Sep 22, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
nelsonic
Oct 20, 2017
Hi! where do the uriEncode and uriDecode functions "live" now? (thanks!)
Edit: found them: http://package.elm-lang.org/packages/elm-lang/http/latest/Http#encodeUri
nelsonic
commented
Oct 20, 2017
•
|
Hi! where do the
|
lukewestby commentedAug 28, 2016
These functions are available in evancz/elm-http but I believe they are more broadly useful - at least as useful as working with URLs in general. An example might be in combination with elm-lang/navigation and evancz/url-parser to deal with query strings. It would be great to be able to build things like query string parsers without including a dependency on evancz/elm-http.
Ordinarily this is a scenario where things would go in string-extra but since these require native calls I figured I'd start here.