Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please, split 'references' and 'run test' options in code editor #10238

Closed
ghost opened this issue Aug 6, 2016 · 3 comments
Closed

Please, split 'references' and 'run test' options in code editor #10238

ghost opened this issue Aug 6, 2016 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debt Code quality issues verified Verification succeeded
Milestone

Comments

@ghost
Copy link

ghost commented Aug 6, 2016

Hi, i think, single option
"editor.referenceInfos": true
for 'references', 'run test' and 'debug test' is not useful.

What if i need to run test from the vscode, but i very don't like 'references'?

Please, split these options to something like
"editor.referenceInfos": true
"editor.debuggingCommands": true

Thank you.

@jrieken jrieken added the bug Issue identified by VS Code Team member as probable bug label Aug 8, 2016
@jrieken jrieken self-assigned this Aug 8, 2016
@jrieken
Copy link
Member

jrieken commented Aug 8, 2016

Wow - that's an blast from the past. Historically we only had backed in reference info and that we have generalised code lens which is contributed from extensions that setting doesn't make sense anymore...

@jrieken jrieken added this to the August 2016 milestone Aug 8, 2016
@jrieken jrieken added the debt Code quality issues label Aug 9, 2016
@jrieken
Copy link
Member

jrieken commented Aug 9, 2016

I have added a new setting codeLens that is better name for what it does - the old value is discouraged but still respected. The information that is shown in code lens depends on the the extensions you install. By default VS Code ships with no code lens provider

@jrieken jrieken closed this as completed Aug 9, 2016
@ghost
Copy link
Author

ghost commented Aug 10, 2016

Thank you

@octref octref added the verified Verification succeeded label Sep 2, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debt Code quality issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants