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

Better code completions #7

Closed
nosami opened this issue Dec 14, 2014 · 10 comments
Closed

Better code completions #7

nosami opened this issue Dec 14, 2014 · 10 comments

Comments

@nosami
Copy link
Contributor

nosami commented Dec 14, 2014

Currently /autocomplete returns a list of symbols ... but only after a '.'

Also we don't get any parameter information or 'snippets'

@nosami
Copy link
Contributor Author

nosami commented Dec 18, 2014

We're currently missing keywords such as public, private, await, linq keywords etc.

Also we need Console.WL to complete WriteLine

@nosami
Copy link
Contributor Author

nosami commented Dec 22, 2014

Attributes should complete without the word attribute, e.g. [Fact] vs [FactAttribute]

@davidfowl
Copy link
Member

/cc @Pilchie

@davidfowl
Copy link
Member

I'm not sure if this makes any sense by parameter intellisense? Maybe we need to expand the response type to support parameter intellisense for method invocations

@Pilchie
Copy link
Contributor

Pilchie commented Dec 23, 2014

Vs treats these at two separate features - completion and signature help. Some other editors (cough eclipse cough) merge them into a single list. I wonder if there shouldn't be a separate endpoint for returning overload info for VS like clients. At the same time, this response probably does need more info to enable eclipse style presentation before a symbol name is chosen.


From: David Fowlermailto:[email protected]
Sent: ‎12/‎22/‎2014 6:16 PM
To: OmniSharp/omnisharp-roslynmailto:[email protected]
Cc: Kevin Pilch-Bissonmailto:[email protected]
Subject: Re: [omnisharp-roslyn] Better code completions (#7)

I'm not sure if this makes any sense by parameter intellisense? Maybe we need to expand the response type to support parameter intellisense for method invocations


Reply to this email directly or view it on GitHub:
#7 (comment)

@davidfowl
Copy link
Member

Lets have separate endpoint then. We should allow editors to do both the VS approach and the snippet approach.

@nosami
Copy link
Contributor Author

nosami commented Dec 27, 2014

Created a separate ticket for snippets #38

@nosami
Copy link
Contributor Author

nosami commented Jan 30, 2015

Need to order completions like this :-

* Completions are ranked in the following order
    * Exact start match (case sensitive)
    * Exact start match (case insensitive)
    * CamelCase completions
    * Subsequence match completions

@anfomin
Copy link

anfomin commented Apr 20, 2016

Is there any updates with attributes autocomplete? Suffix "Attribute" is really annoying.

@nosami wrote on Dec 23, 2014:
Attributes should complete without the word attribute, e.g. [Fact] vs [FactAttribute]

@david-driscoll
Copy link
Member

Resolved by #840

dibarbet pushed a commit to dibarbet/omnisharp-roslyn that referenced this issue Sep 22, 2022
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

No branches or pull requests

5 participants