Re: [elixir-core:11718] Code.eval_string() raises warnings when parsing Mix.lock

2024-03-21 Thread Thibaut Barrère
Thanks Wojtek - I was unsure if this would result in a potential change request (on the format of Mix.lock itself), hence my posting here, but well noted! Thanks for hint as well, that should do! -- Thibaut Le jeudi 21 mars 2024 à 17:14:18 UTC+1, woj...@wojtekmach.pl a écrit : > Please use El

[elixir-core:11716] Code.eval_string() raises warnings when parsing Mix.lock

2024-03-21 Thread Thibaut Barrère
Hello! A slightly exotic use-case, but I would like to have your opinion :-) While doing maintenance work, I often leverage the fact that Mix.lock content is "valid Elixir" to implement useful stuff. Two examples are: - https://github.com/etalab/transport-site/blob/master/generate_deps_changel

Re: [elixir-core:11518] IEx auto-complete on __functions__

2023-09-12 Thread Thibaut Barrère
> `__schema__` is only a partially-public API. I believe it is indeed the culprit ; it is displayed as public on the website, but "technically" not public. > For it to show up in documentation and iex, a PR would need to be accepted > to Ecto that would add a `@doc` attribute to the generated `

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

2022-02-04 Thread Thibaut Barrère
After sleeping on it, I realise that I've come across this specific problem only once, ever, since working with Elixir. Also it reminds me of another case where the doctests were written, but not registered in the test case, causing similar consequences (if I recall well). Maybe there is a broade