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

Keychain Deserialization Errors #161

Merged
merged 11 commits into from
Mar 17, 2018
Merged

Keychain Deserialization Errors #161

merged 11 commits into from
Mar 17, 2018

Conversation

mattrubin
Copy link
Owner

Add an internal throwing initializer for creating a Token from a url, and convert the failable initializer for creating a PersistentToken from a keychain dictionary to a throwing initializer.

This fixes an issue in persistentToken(withIdentifier:) and allPersistentTokens() where deserialization errors would be ignored, causing a persistent token that existed but could not be deserialized to be treated the same as a persistent token that did not exist.

@codecov
Copy link

codecov bot commented Mar 10, 2018

Codecov Report

Merging #161 into develop will increase coverage by 0.04%.
The diff coverage is 90%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop     #161      +/-   ##
===========================================
+ Coverage    95.36%   95.41%   +0.04%     
===========================================
  Files            6        6              
  Lines          475      480       +5     
  Branches        34       32       -2     
===========================================
+ Hits           453      458       +5     
  Misses          22       22
Impacted Files Coverage Δ
Sources/Token+URL.swift 97.4% <100%> (-0.02%) ⬇️
Sources/Keychain.swift 87.75% <87.5%> (+0.52%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f20dc1...5a3c36a. Read the comment docs.

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.

1 participant