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

Improve OmniSharp options #710

Merged
merged 4 commits into from
Aug 24, 2016

Conversation

DustinCampbell
Copy link
Member

  • Add new configuration for OmniSharp-specific options: "omnisharp"
  • Rename "csharp.omnisharp" to "omnisharp.path" (legacy option is still supported)
  • Rename "csharp.omnisharpUsesMono" to "omnisharp.useMono" (legacy option is still supported)
  • Add new option "omnisharp.loggingLevel" which can be set to "verbose". This enables debugging output from the OmniSharp server.

- Add new configuration for OmniSharp-specific options: "omnisharp"
- Rename "csharp.omnisharp" to "omnisharp.path" (legacy option is still supported)
- Rename "csharp.omnisharpUsesMono" to "omnisharp.useMono" (legacy option is still supported)
- Add new option "omnisharp.loggingLevel" which can be set to "verbose". This enables debugging output from the OmniSharp server.
@gregg-miskelly
Copy link
Contributor

Do you want to add these options to the package.json file to light up IntelliSense? Otherwise LGTM

@DustinCampbell
Copy link
Member Author

I actually didn't know that was a thing. 😄 I'll take a look.

@DustinCampbell DustinCampbell added this to the 1.4 milestone Aug 24, 2016
@DustinCampbell
Copy link
Member Author

Thanks for the suggestion @gregg-miskelly. I had completely missed the "configuration" section for package.json files!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants