Fix tagPrefix/vTagPrefix coherence #170
Merged
Conversation
This file contains 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
I thought I'd gotten the defaults right with the coherence checking, but I never wrote a test for it so, inevitably, it wasn't.. Fixed by not giving `dynverTagPrefix` a default value so it's possible to tell if a user set it or not. Now this sets the tagPrefix to "" if vTagPrefix was set to false. If both keys are set, to incoherent values, it will throw.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 thought I'd gotten the defaults right with the coherence checking, but
I never wrote a test for it so, inevitably, it wasn't..
Fixed by not giving
dynverTagPrefixa default value so it's possibleto tell if a user set it or not.
Now this sets the tagPrefix to "" if vTagPrefix was set to false.
If both keys are set, to incoherent values, it will throw.
Fixes #169