search

OmniSharp / omnisharp-roslyn

OmniSharp server (HTTP, STDIO) based on Roslyn workspaces
MIT License
1.77k stars 421 forks source link

Intellisense for project.json / global.json #134

Open nosami opened 9 years ago

nosami commented 9 years ago

We should be able to generate intellisense for these files based on json schemas and nuget feed information.

nosami commented 9 years ago

Just had a look at how the Kulture plugin works.

It's using hardcoded schema information. We should probably use the project.json schema information

It's also using the following url for nuget information. https://www.myget.org/F/aspnetrelease/api/v2/Packages()?$select=Id&$format=json&orderby=DownloadCount&$top=100

We probably also need to use https://nuget.org/api/v2/ and parse Nuget.Config for other feeds?

nosami commented 9 years ago

nuget v3 feeds are working well - http://api-v3search-0.nuget.org/query?q=omni

masaeedu commented 9 years ago

@nosami Is anyone assigned to this?

nosami commented 9 years ago

No. I did hear on the grapevine though that MS might contribute some code to do this //cc @davidfowl

On Tue, May 19, 2015 at 11:35 AM, Asad Saeeduddin notifications@github.com wrote:

@nosami https://github.com/nosami Is anyone assigned to this?

— Reply to this email directly or view it on GitHub https://github.com/OmniSharp/omnisharp-roslyn/issues/134#issuecomment-103432130 .

david-driscoll commented 9 years ago

We have the three new endpoints now /packagesearch, /packageversion, /packagesource. Atom uses a fallback repo https://github.com/OmniSharp/omnisharp-nuget/tree/resources .

Should we have packagesearch use similar behavior to atom (using the fallback) or should that detail be left to each editor to decide?

If we can leave it alone, then we should be able to close this, otherwise we should make an enhancement to packagesearch