IntelliJ Elixir Works Even if your Code Doesn't
summary
The plugin claims an editor should work even when code doesn’t compile and backs it with an independent JFlex lexer and GrammarKit parser that resolves macros in broken files, indexes project beams to find invalid matches, and reduced unresolvable references from 496 to 28 by improving Ecto/phoenix heuristics. It decompiles .beam docs and guards, reads beam files directly for speed, adds a distributed Erlang debugger via jinterface, and supports EEx/HEEx and Elixir 1.12+ syntax and sigils (decompiles .beam docs chunk).
AI-written summary · about
chapters (15)
- 0:00Introduction to the plugin
- 1:29Custom lexer and parser
- 4:13Debugger and version support
- 5:18Template language support
- 8:13Community features and testing
- 9:15Debugger and JInterface
- 11:41Decompiler enhancements
- 15:30Parser error recovery fixes
- 20:37Disassembler and SDKs
- 23:29Dialyzer integration
- 24:22Reference resolution
- 31:07Yakto library testing
- 32:32Syntax and decompiler updates
- 35:15IDE integrations and tools
- 37:09Future work and Q&A
