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

C# IntelliSense Hints are unreadable (new lines are missing) #1057

Closed
marekadamczyk opened this issue Dec 19, 2016 · 10 comments
Closed

C# IntelliSense Hints are unreadable (new lines are missing) #1057

marekadamczyk opened this issue Dec 19, 2016 · 10 comments

Comments

@marekadamczyk
Copy link

  • VSCode Version: Code 1.8.0 (38746938a4ab94f2f57d9e1309c51fd6fb37553d, 2016-12-13T17:45:32.595Z)
  • OS Version: Windows_NT ia32 10.0.14393
  • Extensions:
Extension Author Version
csharp ms-vscode 1.5.3
mono-debug ms-vscode 0.12.0
unity-debug Unity 1.1.0

Steps to Reproduce:

  1. Open any C# project containing sln and csproj file so full IntelliSense will be working.
  2. Hover your mouse over any function containing C# XML Comments with summary, more than one parameter, and return tags.

Below example code and the IntelliSense hint containing parsed XML documentation. If it contains more than one tag (ex. few function parameters + returns) all are displayed in one line therefore it is unreadable. It seems that new lines are missing between <param> and <returns> tags.

code
hint

@marekadamczyk
Copy link
Author

Hi, any news on the issue?

@DustinCampbell DustinCampbell added this to the 1.8 milestone Feb 7, 2017
@DustinCampbell
Copy link
Member

@filipw: Looking at omnisharp-roslyn, I see some weird code related to this. It appears that both the IntelliSenseService and TypeLookupService pass FormattingOptions.NewLine to the DocumentConverter. Any idea why we do that? Is there any reason that DocumentConverter shouldn't just use Environment.NewLine?

@filipw
Copy link
Contributor

filipw commented Feb 7, 2017

it's a leftover from the old OmniSharp server - that's how it behaved originally.
Not sure about the root reason though

@DustinCampbell
Copy link
Member

the behavior is bad though. Shouldn't we change it?

@DustinCampbell
Copy link
Member

it's super bizarre. "Only use line endings like I describe in FormattingOptions, which default to \n".

@DustinCampbell
Copy link
Member

It doesn't fix this problem anyway. I'm wondering if there's something deeper in VS Code that's doing weird things here.

@DustinCampbell
Copy link
Member

I'll investigate this more for 1.8

@filipw
Copy link
Contributor

filipw commented Feb 7, 2017

"Only use line endings like I describe in FormattingOptions, which default to \n".

🙈

@DustinCampbell
Copy link
Member

lol

@akshita31
Copy link
Contributor

akshita31 commented Feb 7, 2018

This issue has been fixed in the 1.14 milestone. We just released a beta of 1.14 - https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.14.0-beta4. Follow these instructions to install a beta release of C# for VS Code.

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

No branches or pull requests

4 participants