Skip to content

json-language-features/CONTRIBUTING.md fixes#73273

Merged
aeschli merged 1 commit intomicrosoft:masterfrom
SamB:json-features-CONTRIBUTING-fixes
May 7, 2019
Merged

json-language-features/CONTRIBUTING.md fixes#73273
aeschli merged 1 commit intomicrosoft:masterfrom
SamB:json-features-CONTRIBUTING-fixes

Conversation

@SamB
Copy link
Contributor

@SamB SamB commented May 4, 2019

In particular, mention npm and yarn as appropriate.
Some of the mentions had apparently been inadvertantly switched???

In particular, mention npm and yarn as appropriate.
Some of the mentions had apparently been inadvertantly switched???
@aeschli
Copy link
Contributor

aeschli commented May 6, 2019

Agree that we should be consistent (either yarn or npm), Yourpull request, however, keeps the inconsistency. Can we use yarn everywhere?

@SamB
Copy link
Contributor Author

SamB commented May 7, 2019

Well, that would be possible, but it doesn't appear to be consistent with what's currently checked into https://github.com/microsoft/vscode-json-languageservice at the moment. In particular, it has a package-lock.json but no yarn.lock. I was just attempting to make the documentation consistent with actual practice.

(Aside: Is it just me, or was there a capital M in microsoft yesterday?)

@aeschli
Copy link
Contributor

aeschli commented May 7, 2019

Ok, I see, you are right. For JSON we still haven't switched from package-lock.json to yarn.lock

@aeschli aeschli self-requested a review May 7, 2019 09:30
@aeschli aeschli added this to the April 2019 milestone May 7, 2019
@aeschli aeschli merged commit 8099c01 into microsoft:master May 7, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants