expert-lsp/expert

Port Refactorex into Expert

Closed

#678 opened on May 13, 2026

View on GitHub
 (2 comments) (2 reactions) (1 assignee)Elixir (103 forks)batch import
good first issue

Repository metrics

Stars
 (1,986 stars)
PR merge metrics
 (Avg merge 13d 12h) (43 merged PRs in 30d)

Description

Refactorex is an excellent project that we depend on for several code actions.

However its original use case was different and integrating it with expert has some compatibility issues, mainly around dealing with offset conversions, or odd corner cases we've found from expert users.

I think it's worth to port its features(with proper attribution) into expert itself for two reasons:

  • To eliminate the compatibility glue and apply expert-specific optimizations where needed
  • To allow us to fix issues quickly, and not put the entire burden on the one maintainer of Refactorex

cc @gp-pereira as the Refactorex author

Contributor guide

Research direction
Inspect Refactorex features and identify which ones to port. Understand the compatibility issues described. Trace the current expert code for code actions and plan integration.
Tech stack
elixir
Domain
backenddeveloper experience
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
ElixirGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40