Uh oh!
There was an error while loading. Please reload this page.
Pvb/discover code actions - #9304
Conversation
… variables and parameters
easier to change in the future.
There was a problem hiding this comment.
seems more Javascripty to use an interface instead of a class for CodeActionContext and say
constcontext={ error, sourceFile,spec: { start,length: end-start}, checker };since CodeActionContext doesn't use any class features except the constructor.
…/discoverCodeActions
…nto pvb/discoverCodeActions # Conflicts: # src/harness/fourslash.ts # src/services/quickfixes/quickFixProvider.ts # src/services/services.ts # src/services/tsconfig.json
…into pvb/discoverCodeActions # Conflicts: # src/services/codefixes/references.ts
… fix through text changes
Fix up all the tests
Fixes due to API Changes
Alex Eagle (alexeagle)
commented
Jul 15, 2016
I'd like to try this out, is there any way to get a fix to appear outside of the test suite, or manual interactions with the language service protocol? Maybe a branch of VSCode that knows to ask TS lang services for fixes? |
Paul van Brenk (paulvanbrenk)
commented
Jul 18, 2016
Alex Eagle (@alexeagle) Not yet unfortunately, VS Code is next on my list after I'm done with the VS integration. |
Alex Eagle (alexeagle)
commented
Jul 18, 2016
Thanks, I just wrote a small program using the LanguageService to try it On Mon, Jul 18, 2016 at 9:52 AM Paul van Brenk notifications@github.com
|
# Conflicts: # src/services/services.ts
Paul van Brenk (paulvanbrenk)
commented
Aug 5, 2016
Closing this in favor of more smaller PRs #10185 |
Script side to enable codeaction for error codes, needs Dev15 changes