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

#233 npm v3 support, #308 VS2015 RTM exceptions on project load #386

Merged
merged 6 commits into from
Aug 27, 2015

Conversation

mousetraps
Copy link
Contributor

#233 npm v3 support

  • support solution explorer tree view
  • analysis depth optimizations
  • add .staging to ignored directories
  • ensure global scope visibility is not limited during analysis
    VS2015 RTM Exceptions on Project Load #308 VS2015 RTM exceptions on project load
  • ensure key is not null before adding package

The bulk of the changes are there, but note that this is not a comprehensive npm v3 changeset - still need to...

  • write unit tests to verify npm tree
  • fix require intellisense to show fewer completions.

These changes are not as risky, though, so I'll file RTM issues for these items if I can't get to them today.

- support solution explorer tree view
- analysis depth optimizations
- add .staging to ignored directories
- ensure global scope visibility is not limited during analysis

microsoft#308 VS2015 RTM exceptions on project load
- ensure key is not null before adding package
_analysisIgnoredDirs = ignoredPaths.Split(';').Select(x => '\\' + x + '\\').ToArray();
} else {
_analysisIgnoredDirs = new string[0];
_analysisIgnoredDirs.Append(ignoredPaths.Split(';').Select(x => '\\' + x + '\\').ToArray());
Copy link
Member

Choose a reason for hiding this comment

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

Is _analysisIgnoredDirs just a list? How often is this function called? Is there a risk here of repeatedly appending to the list over time? (If it's a set, this seems safe).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It gets called on project load, and the ProjectNodes don't get reused on Reload, so it's effectively set.

- updated based on CR
- refactored a bit to make things clearer
- move RequireAnalysisUnit work to analysis thread to prevent off-thread mutations
- add another format for top-level requiredBy string "/"
- fixed other misc. issues that came up during testing
- fix issue where some npm trees were not getting created when nodes were duplicated
…o npm3

Conflicts:
	Nodejs/Product/Nodejs/Extensions.cs
@billti
Copy link
Member

billti commented Aug 27, 2015

Code looks good. I'll merge it in and test it. Thanks!

billti added a commit that referenced this pull request Aug 27, 2015
#233 npm v3 support, #308 VS2015 RTM exceptions on project load
@billti billti merged commit 05b51f5 into microsoft:master Aug 27, 2015
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.

4 participants