-
Notifications
You must be signed in to change notification settings - Fork 336
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
[issue 679][oauth2] Fix macos compiler warnings, remove store impleme… #737
base: master
Are you sure you want to change the base?
Conversation
…nt keyring which not used at all
Any change to confirm PR ? |
@wolfstudy can you confirm this PR? thanks |
cc @zymap Please take a look thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a persistent implementation, we shouldn't remove it. It's an option of the store implementation, user can choose by themselves.
@zymap I got it and understand your point. If it should be kept for the users which choose this implementation, now what's your opinion about the users not use this extra implementation and still shown the warning below? It is really annoying when you develop and run the program in every time. |
I saw the author has fixed this issue(keybase/go-keychain#76). Could you please try to upgrade the dependency to check if it works? |
@zymap I just run:
This is the official way to init, it should be all right. If I run my program, the errors shown like this: You said the new version of It should be good. But I got some new errors which looks worse: By the way. My mac OS version From my perspective, the warning problem was not fixed yet or not effective. |
@llqgit I think they remove the support to avoid the warning. keybase/go-keychain#76 |
…nt keyring which not used at all
Master Issue: #719
Motivation
Fix MacOS version warning from the unused OAuth2 store implement named keyring.go
Modifications
To fix the warning that on MacOS once for all by remove the
keyring.go
which no references from other places, rather than upgrade the keyring package.Verifying this change
This change is already covered by existing tests, such as (please describe tests).
Does this pull request potentially affect one of the following parts:
github.com/99designs/go-keychain
Documentation