We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We successfully included the library in our tool - JabRef/jabref#10044
I checked the output in Windows 10's Credential Manager:
I wonder about the `|'
Logitech uses / for separation:
/
Microsoft adds some key-value stuff, but I like the Logitech one better --> is it possible to replace the | with a /?
|
I would like to have / as separator in Windows, too. Looks nicer 😅.
Code:
java-keyring/java-keyring/src/main/java/com/github/javakeyring/internal/windows/WinCredentialStoreBackend.java
Line 59 in 77358e9
Did not submit a PR right away, because I don't know about failing test cases. Wanted to note down the feature wish.
When implementing, the code should have backwards compatibility turned on and at reading, it should check first for /, then for |.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We successfully included the library in our tool - JabRef/jabref#10044
I checked the output in Windows 10's Credential Manager:
I wonder about the `|'
Logitech uses
/
for separation:Microsoft adds some key-value stuff, but I like the Logitech one better --> is it possible to replace the
|
with a/
?I would like to have
/
as separator in Windows, too. Looks nicer 😅.Code:
java-keyring/java-keyring/src/main/java/com/github/javakeyring/internal/windows/WinCredentialStoreBackend.java
Line 59 in 77358e9
Did not submit a PR right away, because I don't know about failing test cases. Wanted to note down the feature wish.
When implementing, the code should have backwards compatibility turned on and at reading, it should check first for /, then for |.
The text was updated successfully, but these errors were encountered: