This repository has been archived by the owner on Nov 3, 2020. It is now read-only.
Lockfile version checking #257
Merged
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
nwest
force-pushed
the
lockfile-version-checking
branch
2 times, most recently
from
0ddfbb2
to
4db45fb
Compare
Adjust height of the warning label to be based on the warning content
nwest
force-pushed
the
lockfile-version-checking
branch
from
4db45fb
to
4eb6d0a
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Closes #249.
LockfileLockfileA good way to test this is to edit a
Podfile.lock's CocoaPods version to something (say1.1) and open the Podfile in the app. It takes a bit of time to get info back from the bridge.