Wojtek Mach

Results 81 issues of Wojtek Mach

**Describe the bug** ```erlang 1> uri_string:parse("http://localhost/A|B"). {error,invalid_uri,":"} ``` Per docs: > The third component is a term providing additional information about the cause of the error. however in this case...

team:PS
enhancement
stalled
bug
priority:low

### Reviewers r? @ cc @stripe/developer-products ### Summary Besides exiting programs on SIGTERM/ctrl+c, it's common to exit on closing stdin/ctrl+d.

Extracted from https://github.com/elixir-lang/ex_doc/pull/1818#issuecomment-1822395188. I think we have all the ingredients: 1. GitHub code edit links may contain line numbers, notice the editor cursor is at line 3: https://github.com/elixir-lang/ex_doc/edit/main/lib/ex_doc/markdown.ex#L3 2. Remix...

As a reminder, we want to replace, say, `atom()` with `atom()`. The challenging part was we wanted to also _format_ the type specs (using Code.format_string, erl_pp) and preserve that text...

Currently the contract is `Req.request(req) :: {:ok, Req.Response.t()} | {:error, Exception.t()}`, that is, users of the library might get arbitrary exceptions. In recent releases we added a few Req exceptions:...

Right now we special case `:headers` and `:params`. For example: ```elixir Req.new(headers: [a: 1]) |> Req.merge(headers: [b: 2]) == Req.new(headers: [a: 1, b: 2]) ``` Another one when this might...

Ref: https://github.com/livebook-dev/livebook/pull/2497/files

Note to self: check `defp supported_accept_encoding`.

I keep forgetting this is not a thing and needs to be `headers: [accept: "application/json"]`. If we do this we could remove `range` step in favour of setting `headers: [range:...

Currently we have have pairs of append and prepend functions for each type of steps, `Req.Request.append_request_steps/2`, `Req.Request.prepend_request_steps/2`, ... My idea of `Req` and `Req.Request` separation is the former is what...