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

Move project.json dependency completion & hover to vscode-omnisharp #224

Closed

Conversation

aeschli
Copy link
Contributor

@aeschli aeschli commented Apr 20, 2016

Until now the code that drove intellisense for dependencies in project.json was sitting in the JSON extension.
We want the omnisharp extension to take ownership.
This pull request implements a completion provider and a hover provider using the newly created 'jsonc-parser' node module that does the JSON file processing.
It gets nuget packages from the nuget API, but is not aware of any nuget configuration files.

In the future the omnisharp extension can also consider to power the completions and hovers directly from the omnisharp server.

We will remove the project.json completion support from the JSON extension for the coming release (end of April).

@aeschli
Copy link
Contributor Author

aeschli commented Apr 20, 2016

Remarks:

  • upgrading vscode dependency to 0.11.0 to use the new vscode API CompletionList. Along with that change, adding node ./node_modules/vscode/bin/install to postinstall to always fetch the vscode.d.ts that matches the dependency.
  • upgrading typescript to 1.8.9 to use the new export type = "a" | b" syntax that is used in jsonc-parser - d.ts. If you don't like that change, then I can look into not using that syntax in jsonc-parser

@gregg-miskelly
Copy link
Contributor

Master is currently locked down. I will follow up over email.

@aeschli
Copy link
Contributor Author

aeschli commented Apr 20, 2016

Ok, I'll wait with removing our support until your stream is open again.

@aeschli
Copy link
Contributor Author

aeschli commented May 27, 2016

Any updates here?

@troydai
Copy link
Contributor

troydai commented May 31, 2016

Hi, quick question here. I notice that spaces and tabs are mixed as indents in C# extension source code. Looks like in this PR every indentation is a tab. Just wondering do we have a guideline in place in terms of tab vs spaces? If not, I think it would be nice to settle on one (cough, space, cough).

import * as nls from 'vscode-nls';
const localize = nls.loadMessageBundle();

const FEED_INDEX_URL = 'https://api.nuget.org/v3/index.json';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it possible to export this value and make it configurable?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that would be a future improvement. The feeds to use should probably be picked up from nuget.config

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 cool.

@aeschli
Copy link
Contributor Author

aeschli commented Aug 2, 2016

@gregg-miskelly Any update here? Please let me know when I can remove the project.json code on the VSCode side...

@aeschli
Copy link
Contributor Author

aeschli commented Feb 7, 2017

@gregg-miskelly @DustinCampbell Any updates here?
Is it ok if I remove our project.json suggest code from VSCode?

@gregg-miskelly
Copy link
Contributor

@DustinCampbell this is more your area, so I will leave this to you.

@DustinCampbell DustinCampbell mentioned this pull request Feb 13, 2017
5 tasks
@DustinCampbell
Copy link
Member

@aeschli: Sorry for the delay. This definitely won't merge cleanly, so I'm going to take this week and migrate your changes.

@DustinCampbell
Copy link
Member

Closing in favor of #1236.

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.

5 participants