Repository navigation
Port Refactorex into Expert #678
Description
Activity
I wonder if we have any more detailed vision for that? Just put the current Refactorex code somewhere and refer to it? Or take the Refactorex features one by one and port them into more Expert-native form? Currently we have 5 PRs open to Refactorex with fixes to bug found in Expert usage, so I think it would be good to address soon, even if no one volunteers for "good first issue".
Any of them works, vendoring it inside
appsand fixing its crashes works as a first step.
In the long term I think we want to go over its refactors and port them into a more Expert-native form but I don't think that is required for now.
The end goal is to be able to fix the issues we have related to it- added a commit that references this issue
on Jul 1, 2026 - added a commit that references this issue
on Jul 2, 2026
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:
cc @gp-pereira as the Refactorex author