`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:

• [ ] https://github.com/dotnet/fsharp/issues/15563

Ideas for the ones:

• [ ] https://github.com/dotnet/fsharp/issues/2836
• [ ] https://github.com/dotnet/fsharp/issues/15562
• [ ] https://github.com/dotnet/fsharp/issues/15564
• [ ] https://github.com/dotnet/fsharp/issues/15565
• [ ] https://github.com/dotnet/fsharp/issues/15566
• [ ] https://github.com/dotnet/fsharp/issues/15673

Done:

• [x] https://github.com/dotnet/fsharp/issues/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 :)