Elixir Meetup #4 ▶ hosted by Curiosum ▶ Michael Lubas & Bartosz Górka
if !Enum.member?(satisfied_employees, you), do: you.read()
IntellIJ Elixir v12.2.1
Changelog
v12.2.1
Bug Fixes
-
-
Don’t call
.navigationElement
to prevent unnecessary decompilation when resolving references or showing completions.-
Don’t call
navigationElement
inChooseByNameContributor
-
Don’t decompile Protocols to get their specific
t
type -
Don’t call
.navigationElement
when resolving built-in types in:erlang
-
Don’t use
navigationElement
inCallDefinitionClause.implicitImports
forKernel
andKernelSpecial.Forms
. -
Don’t call
.navigationElement
inreference.resolver.Module.multiResolveProject
Prevents decompiling modules when doing completion.
PsiCompiledElement
in places that previously only handled source and decompiledCall
s-
getElementDescription
for ModuleImpl - Complete call definition under binary modules
- Don’t look for variables in compiled elements
- Don’t assume elements have a non-null node Decompiled elements don’t
-
Index
TypeDefinition
s in .beam files Only supported built-in types faked in:erlang
for now -
Walk
ModuleImpl
forscope.Type
-
Don’t call
-
Don’t call
Read next if !Enum.member?(satisfied_employees, you), do: you.read()