[elixir-core:11513] IEx auto-complete on __functions__

2023-09-06 Thread thibaut...@gmail.com
Hi! Today during a session I was caught a bit off-guard by the fact that completion doesn't tell you about __schema__ on an Ecto module. (although the behaviour is clearly documented in IEx

[elixir-core:10750] Should this result in a warning?

2022-02-03 Thread thibaut...@gmail.com
Hello, While debugging some doctests I haven't written initially myself, I realised that one can create doctests that are bogus and will be skipped quite easily, just like this: ## Examples iex > SomeModule.some_method("param") "expected_output" The culprit is the extra space between "iex"

Re: [elixir-core:10543] IEx and pipes ergonomics (with Ecto)

2021-11-25 Thread thibaut...@gmail.com
attern matching likely would fail (because we would execute the > pattern multiple times). > > Please open up an issue anyway, it probably merits investigation. > > On Thu, Nov 25, 2021 at 09:13 thibaut...@gmail.com > wrote: > >> Forgot to reply on this: >> &g

Re: [elixir-core:10541] IEx and pipes ergonomics (with Ecto)

2021-11-25 Thread thibaut...@gmail.com
ine is a |> (but there are probably tons of edge cases if we start dealing with this...). Anyway - thanks for the clarification! -- Thibaut Le mercredi 24 novembre 2021 à 18:37:22 UTC+1, thibaut...@gmail.com a écrit : > Hi, > > > There is nothing we can do unfortunately, withou

Re: [elixir-core:10540] IEx and pipes ergonomics (with Ecto)

2021-11-24 Thread thibaut...@gmail.com
Hi, > There is nothing we can do unfortunately, without perhaps changing upstream (i.e. how the Erlang shell system works) I understand ; thanks for the explanation ! We will use work-arounds for now. -- Thibaut Le mercredi 24 novembre 2021 à 17:52:44 UTC+1, José Valim a écrit : > No, it is

[elixir-core:10535] IEx and pipes ergonomics (with Ecto)

2021-11-24 Thread thibaut...@gmail.com
Hello, A coworker (new to Elixir) was quite surprised today when pasting this code into IEx: import Ecto.Query a = DB.Resource |> where([r], not is_nil(r.datagouv_id)) |> group_by([r], r.datagouv_id) |> having([r], count(r.datagouv_id) > 1) |> select([r], r.datagouv_id) |> DB.Repo.all()

Re: [elixir-core:10461] Proposal: programmatic access to the exact Mix.install/2 installation folder

2021-09-25 Thread thibaut...@gmail.com
r the answer! -- Thibaut > > On Sat, Sep 25, 2021 at 5:23 PM thibaut...@gmail.com > wrote: > >> Hello, >> >> Currently, Mix.install/2 installs the dependencies specified by the user >> under a folder whose name is built based on 3 elements: >> >&

[elixir-core:10459] Proposal: programmatic access to the exact Mix.install/2 installation folder

2021-09-25 Thread thibaut...@gmail.com
Hello, Currently, Mix.install/2 installs the dependencies specified by the user under a folder whose name is built based on 3 elements: - an install root (e.g. ~/Library/Caches/mix/installs), optionally overridable via MIX_INSTALL_DIR env variable - the version of elixir and erlang