Parsing HTTP Link header with NimbleParsec

Another naive example at Tesla.Middleware.DecodeRels:"

src

  defp rels(link) do
    link
    |> String.split(",")
    |> Enum.map(&String.trim/1)
    |> Enum.map(&rel/1)
    |> Enum.into(%{})
  end

  defp rel(item) do
    Regex.run(~r/\A<(.+)>; rel="(.+)"\z/, item, capture: :all_but_first)
    |> Enum.reverse()
    |> List.to_tuple()
  end

haha, I already did (initially published to hex @ March 30, 2019):

but it has a generator as well as a parser. The forum showed me this thread as related when I was creating that thread about it

NimbleParsec can output the compiled module, so users don’t need nimble_parsec as dependency, if that’s the reasoning here.

Okay, now I added LinkParser.parse_naive/1 to just use core modules (e.g. String, Enum, …).

It passes some tests, but it doesn’t implement something - e.g. it allows any chars in the token (compared to NimbleParsec version checks allowed chars)