v14.0.1

Bug Fixes

• Ignore atoms at top-level when looking for docs.

• Replace TODO() in leex.reference.resolver.Assign with logger errors that include PSiElement.

• Ignore type for docs.

• Don’t look for variable use scope above EEx tags. If a variable is declared in an EEx tag then it is actually missing its declaration and cannot be resolved, so ignore its usage.

• Check if module is disposed when write action is run for syncLibraries.

• Only use Elixir SDK for mix format if it has an Erlang SDK.

• Include more lines of context for stacktraces in error reports.

• Ignore identifier when @*doc attribute isn’t quoted.

• Ignore if package virtual file is disposed before the deps can be read.

• Don’t decompile Erlang And as Elixir and.

• Ignore request_body and responses for docs.

• Check if heredoc has lines before calculating host text range for Markdown docs.

• Ignore if stubs ids can’t be found when resolving Callables.

• Ignore hexadecimal numbers at the root of the file when collecting doc comment.

• Return an empty array of primaryArguments instead of array with null operand for unary operation without operand.

• Set sinceBuild to IntelliJ IDEA 2022.3. Fixes incorrect compatibility listed with < 2022.3 when < 2022.3 support was removed in 14.0.0 with #2946.

• Use minByOrNull to protect from empty module list. This fix may not work as the line number reported in the errors is actually outside of the file. This is only a guess that minBy was what was throwing the NoSuchElement exception.

• Ignore null operands for not in primaryArguments(). Instead of including both left and right operand always and so having null operand in fixed size array return array with only non-null operands.

• Don’t allow Elixir SDK without Erlang SDK to be selected for New Project. The SDK has to be able to work for mix new.

• Ignore strings, charlists, and sigils at the top of file when looking for doc comments.

• Ignore top-level Aliases when collecting docs.

• Ignored unquote calls when injecting docs.

• Find enclosing quote when defs are inside an fn as in Phoenix Route Helpers.

• Handle binary modules when processing protocols and implementations for line markers and definition search.

• Skip unqualified no arguments calls when Ecto.Query.from arguments are being typed.

• Setting name on a call definition clause sets the name on the head instead. The JetBrains API both renames the usage references AND the original element where the rename refactoring was started, but when started on a call definition clause the functionNameElement is the def, defp, defmacro, or defmacrop and so both the name of the call was changed, but the def* was also changed to the new name. Now, if setName is called on a definition, the head is renamed instead.

• Filter out Elixir SDKs that don’t have an Erlang SDK when importing projects.

• Check Elixir SDK has Erlang SDK before running dialyzer. Notify user of configuration error instead of throwing exception when constructing mix commandline.

• Log heredoc where Markdown cannot be injected.

• Don’t inject Markdown in empty heredoc docs.

• Log if new name element type does not match old name element type.

• Replace name with relative identifier instead of identifier for qualified calls on rename.

• Keep looking for variants above if and unless if and unless used to call keepProcessing() after checking if the child calls when resolving or searching for variants, but Variants returned false always from keepProcessing().

  This stops the variant search from terminating inside of an if or unless when it wouldn’t outside of one as was reported in #2751.

• List Kernel and Kernel.SpecialForms variants inside modulars. Keep processing at end of modulars when looking for variants, which will check the implicit imports of Kernel and Kernel.SpecialForms.

• Prevent listing variants from outer module in nested module

• Log the accumulated and target usage type that cannot be folded.

• Fix reporting mix new errors as notifications

  • Don’t associate mix new errors with new project as it doesn’t have a frame, so the notification was suppressed before.
  • Strip color codes from mix new error notification.

• Validate –app is set correctly for new projects

  • If inferred from project name, make sure the name is valid application name the same as mix new does.
  • If –app is set explicitly, make sure it follows naming rules for mix new.