Tracking: Code Refactorings

[psfinaki]

Note
This is a "meta" issue for tracking purposes since GitHub does not support special types of issues.

Code refactorings are code actions that are available but not necessary to be used. In VS, they are represented by screwdrivers.

We should make them easy to create, test, and extend.

Improvements for existing ones:

• Make "add type annotation" code refactoring applicable to all params #15563

Ideas for the ones:

• quickfix/refactor idea: convert Record to class with properties #2836
• A code refactoring for explicit return type annotation #15562
• A code refactoring to deinterpol a string #15564
• A code refactoring to pull a function/type into a signature file #15565
• A code refactoring to convert bool to a Yes|No DU #15566
• Code refactoring: single case union deconstruction #15673

Done:

• Quick action to explicitly annotate a let binding parameter #10421

[kerams]

I have a tip for one: having written a new function/type, use the screwdriver to pull it into an existing signature file.

Or what about extracting a bool function parameter into a Yes | No RQA union type.

[psfinaki]

@kerams absolutely - great ideas both, I created tickets for them.

We'll see when we get to this, and this will also require some new testing machinery. OTOH, we only have 3 code refactorings right now so I don't see major code overhaul happening there as it is happening now in code fixes :)