Make the limitation that only advanced string fields starting with "KPH: " are returned optional #232
Conversation
This file contains hidden or 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
Contributor
Author
|
The "Advanced" tab of the options dialog looks like the following with this changes:
The option defaults to |
pfn
added a commit
that referenced
this pull request
Dec 30, 2015
…imitation Make the limitation that only advanced string fields starting with "KPH: " are returned optional
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I use KeePassHttp in some "script-workflows" to retrieve credentials from KeePass together with KeePassHttpCli - also, I often need values from custom-string-fields, but I don't want them all to be prefixed with "KPH: ".
So I think it would be great to have this limitation optionally.