In particular you said “ We keep track (of) a certain number of editing ‘sessions’“. Is it all local, or is there a cloud service out there somewhere that does all the heavy lifting? I’m wondering though, where’s the processing happening. It’s been a while since I’ve looked at it, so hopefully I haven’t got that wrong. The storage mechanism should have been C# (or maybe VB, or whatever language was being used), not Javascript. I’ve definitely wished for some better way of doing repetitive code refactoring tasks since macros were taken away (yes, I know there’s an extension, but it’s not the same as it used to be). And also for repetitive refactoring of code that may be inherited. Hey Mark! This sounds like it’d be great for detecting duplicate code, on the fly as it were. I’d be very interested to talk with you further about this – drop me an email at mwthomas at microsoft dot com and we can continue the conversation? We’re considering adding a new level for suggested actions that would have a stronger visual treatment than the “suggestion” level. However we recognise this can cause confusion with real compiler warnings, so we are considering what the right level for these suggested actions should be.
We found that nobody was discovering the suggested action at this level, and we’re experimenting with the higher visibility of the “warning” level in the current version. We did experiment internally with using the “suggestion/info” level – which you can see at 11:41 in my demo at, the three little grey dots in the editor. We realize that mixing these suggested actions with the “warnings” level of feedback in the editor can be problematic. Thanks a lot for your feedback Andi, and for trying out the new refactorings feature. When sending your feedback it would be really useful if you can share details of what was detected and what sort of edits you were making we’ll follow up. We’re interested to hear feedback about the recommendations themselves, the performance of the feature, or any capabilities you might be missing.
Please raise issues and comments via Visual Studio “report a problem”. We would love to hear about your experiences as you try this new feature. If you don’t like a suggested change you can select the ignore option on the lightbulb, and we won’t bother you about that detected pattern again unless you recreate it. This syntactic awareness allows it to detect cases where the variable names in your refactoring examples differ but the essential structure of the change is the same: This isn’t just tracking text changes – IntelliCode is aware of the syntactic structure of your code. More details will be presented at the upcoming OOPSLA 2019 conference. The underlying technology is similar to the Excel’s Flash Fill feature and is described in this research paper. The lightbulb offers actions to apply the refactorings for you. When IntelliCode discovers that it can apply one of these scripts elsewhere in your code (which can be based on as few as 2 examples in your code), we let you know via the Visual Studio lightbulb in the margin or when hovering the affected code, and through green “squiggles”. It uses PROSE (PROgram Synthesis by Example) to synthesize generalized edit scripts that can take your code from the “before editing” state to the “after”. Under the hood, IntelliCode looks at each of your edits as you type. Once you change this setting, close any files you may have open, then restart Visual Studio: Visit the Tools-Options page, IntelliCode General tab, Preview features area, and switch C# refactorings to “Enabled” to turn it on. Refactoring is a preview feature of IntelliCode, so when you get Visual Studio 2019 version 16.3 Preview 3 it will be off by default.
0 kommentar(er)
