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

fix : Restore does not generate lock file on NoOp #2799

Merged
merged 6 commits into from
Apr 17, 2019

Conversation

heng-liu
Copy link
Contributor

Bug

Fixes: NuGet/Home#7807
Regression: No

  • Last working version:
  • How are we preventing it in future:

Fix

Details: Add validation of checking the existence of package lock file. If not, failed the no-op.

Testing/Validation

Tests Added: Yes
Reason for not adding tests:
Validation:

Note: the message of "Writing packages lock file at disk." will not be displayed by default if it's dotnet restore. But if add "-verbosity normal", then the message will show up.

@heng-liu heng-liu requested a review from nkolev92 April 16, 2019 15:35
Copy link
Member

@nkolev92 nkolev92 left a comment

Choose a reason for hiding this comment

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

👏

Nice test cases.

@heng-liu heng-liu merged commit 8bcab60 into dev Apr 17, 2019
@heng-liu heng-liu deleted the dev-hengliu-fixRestoreNoopNoLockFileGenerated branch April 17, 2019 05:24
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.

If lock file is deleted, restore does not generate lock file on NoOp
3 participants