elm/url

Issues

• Allow ignoring the path / Just parsing query parameters

  #17 opened 6 years ago by robinheghan
  8

• Support protocols different from http / https

  #10 opened 6 years ago by Gozala
  29

• Url.percentEncode can throw errors

  #54 opened 2 years ago by lydell
  0

• Should "+" in query parameters be parsed as space?

  #32 opened 4 years ago by EvenAR
  11

• Parsing URLs with IPv6 host

  #12 opened 6 years ago by aryszka
  9

• s : Maybe String -> Parser a a

  #53 opened 3 years ago by domenkozar
  0

• missing </> import in docs for Url.Parser.parse

  #52 opened 3 years ago by BrianHicks
  0

• When should percent decoding occur by default with paths?

  #42 opened 4 years ago by evancz
  4

• Build relative URLs with "dirty" paths

  #48 opened 4 years ago by aminnairi
  0

• Support for username and password

  #47 opened 4 years ago by pravdomil
  0

• Relative links

  #46 opened 4 years ago by pravdomil
  0

• path should also be escaped

  #25 opened 6 years ago by domenkozar
  5

• Document that only query parameters are percent-encoded

  #43 opened 4 years ago by j-maas
  1

• Incorrect example for Url.Parser.Query.map function.

  #38 opened 4 years ago by akoppela
  2

• s should call percentDecode before matching segment

  #20 opened 4 years ago by malaire
  2

• Support Hash-Routing (again)

  #24 opened 6 years ago by andys8
  1

• package docs mention non-existing Browser.fullscreen

  #39 opened 4 years ago by youlam
  1

• Docs for Url.Parser.Query.custom mention non-existing List.maybeMap

  #27 opened 4 years ago by Janiczek
  2

• add alternative methods to handle a basepath like "some/path/"

  #14 opened 6 years ago by sporto
  4

• Update example for 0.19

  #8 opened 4 years ago by andys8
  2

• Allow parsing the complete 'pathname' at once

  #9 opened 6 years ago by rl-king
  0

• Url.Parser.string does not decode the value

  #16 opened 6 years ago by tomstejskal
  1

• Allow ignoring the rest of path

  #19 opened 6 years ago by malaire
  1

• Use percentEncode on path segments in Url.Builder

  #41 opened 4 years ago by edkv
  1

• Builder should return Url

  #23 opened 6 years ago by j-maas
  8

• fromString Parser not strict enough

  #40 opened 4 years ago by twerkmeister
  1

• Two "?"s added to url

  #37 opened 5 years ago by MartinSStewart
  1

• Incorrect docs for Url.Parser.query

  #36 opened 5 years ago by malaire
  0

• fromString incorrectly deems invalid URL string as a URL

  #33 opened 5 years ago by supermacro
  1

• Please expose Url.Parser.prepareQuery

  #29 opened 5 years ago by robx
  1

• Package not available

  #4 opened 7 years ago
  4

• Url.Builder.absolute doesn't use Url.percentEncode but the Url.percentEncode docs claim that it does.

  #21 opened 6 years ago by jessta
  1

• Url.Parser.parse seems to have wrong type signature

  #22 opened 6 years ago by zeninpalm
  1

• First argument to `custom` is not used any more. Caused confusion among some users.

  #6 opened 6 years ago by wking-io
  1

• Currently not possible to create a websocket url

  #5 opened 7 years ago by ChristophP
  1