Extend API to give suggestions that can be used to refactor to fix warnings
See original GitHub issuehttps://github.com/fsprojects/VisualFSharpPowerTools/issues/1130
A warning returned from the API should be extended to include optional information on how the warning could be fixed e.g. from
text, to
text and positions of both - if there’s no value then the fix needs to be done manually/is not yet implemented
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Refactoring source code in Visual Studio Code
In VS Code, Code Actions can provide both refactorings and Quick Fixes for detected issues (highlighted with green squiggles). An available Code Action...
Read more >refactor to "move to another (existing) file" · Issue #29988 · ...
My suggestion meets these guidelines: This wouldn't be a breaking change in existing TypeScript/JavaScript code
Read more >Refactoring made easy with IntelliCode! - Visual Studio Blog
Illustration showing how IntelliCode can detect patterns syntactically and offer suggestions. If you don't like a suggested change you can ...
Read more >Introduction to refactoring | IntelliJ IDEA Documentation
If you find a public method that appears to be unused but does form part of a public API, it should be covered...
Read more >Eclipse: Most useful refactorings [closed]
1) Rename - It works on method names, variable names, class names, fields-- really anything with a name. 2) Convert Anonymous Class to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah awesome. For just the hints to start with, I don’t think it’ll be too much work as the linter already know which parts need to be shuffled to get the end result. I think we just need the ranges for each part of both sides of the hint (the match, and the suggestion), which we can get when the hints are matched
I’ll try to make a start on a branch, hopefully something rudimentary by the end of the weekend 🐣
I mean, all I’d need is pre-release nuget package 😉