fix: read package manifest when verifyStoreIntegrity is false #5157
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We need to cover it with a test |
|
Yep, I ll add a test 👍 |
zkochan
reviewed
Aug 4, 2022
zkochan
reviewed
Aug 4, 2022
|
Please add changesets |
zkochan
approved these changes
Aug 4, 2022
|
Congrats on merging your first pull request! 🎉🎉🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue where
verifyStoreIntegrityis set tofalse. The problem was thatcheckFilesIntegrityis called with a deferred promise which is expected to be resolved, however, it was not. This PR makes sure that if integrity checks are disabled that it will still read the package manifest and resolve the promise properly.