mirror of
https://github.com/WhatsApp/erlang-language-platform.git
synced 2025-12-23 12:26:48 +00:00
8d0c680127
Summary: # Context The "Analyze Stacktrace" functionality was broken for a long time. A user attempted to use it and reported it was not able to extract a stacktrace. # Solution This diff restore the basic functionality by: * Refactoring some private code so it's testable * Adding a unit test for the stacktrace extraction * Updating the regex that was used to identify stacktraces in the terminal * Adding an E2E tests * Making the opening mechanism more solid Despite of this, the functionality is quite fragile. I am considering if we should drop it altogether, instead. Reviewed By: alanz Differential Revision: D69518411 fbshipit-source-id: d6270e1e41ae357f6cea4f18f277b35d255bf2d6 |
||
|---|---|---|
| .. | ||
| buck_tests | ||
| buck_tests_2 | ||
| custom_build_tool | ||
| diagnostics | ||
| end_to_end | ||
| eqwalizer/src | ||
| eqwalizer_callers | ||
| eqwalizer_tests | ||
| in_place_tests | ||
| linter | ||
| linter_bad_config | ||
| parse_error | ||
| standard | ||
| .gitignore | ||
| README.md | ||
Fixture erlang projects for e2e tests.
The key to confine ELP to a non-waserver project is to have:
- rebar.config
- .rebar.root
- build_info plugin (for now copy-pasted from waserver)
From this directory, you can manually test:
% elp parse-all --project . --to ~/tmp
Automated tests live in crates/elp/bin/main.rs
See also //whatsapp/elp_test/README.md for additonal end-to-end LSP tests.