Changed passcodeConfiguration from private to public #62
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.
Changed Variable Implementation from private to public. This allows developers to check to see if a passcode is present to determine if they want to show a specific view or not. I personally used this in a method that follows below
This is a special case I have where running something like
passcodeLockPresent!.presentPasscodeLock()
can't be used. In this case above I was calling on:This Commit/PR would make it easier on the developer to determine if the user has a passcode such as in the case above.
For those wonder, '[lock hasPasscode];' with the modifications I made looks like this:
Thanks for taking a look at this PR! Please let me know if you need me to explain anything!