Łukasz Samson

@phewitt Please try setting `dialyzerEnabled` to `false`. Otherwise you can try to fix/ignore your warnings ;)

Probably we need to limit the number of diagnostics we are sending to the client to some reasonable number.

There may be a resolution coming up upstream https://github.com/elixir-lang/elixir/issues/10983

As a workaround you can change your mixfile and force elixir to compile them. Or you can hack elixir-ls to load exs files on build. We do that in debugger....

> For .exs files, you can at least call Code.string_to_quoted to parse it and get at least syntax feedback. That's a good idea @josevalim

Will it not block formatter when build is in progress?

> I don't quite understand the code above, could you give me some insights? Thanks. I don't really know that part either. @axelson, can you help here? Do you think...

@kasvith @KaranAhlawat you are hitting a limitation in elixir_sense. It has only a limited understanding of macro generated code. In order to have first class support for Absinthe it would...

@stefanluptak this looks like a separate issue

Quickfix import, alas and require would definitely be useful. Unfortunately I don't think it's doable without compilation traces (which means elixir >= 1.10).