-
Notifications
You must be signed in to change notification settings - Fork 654
Address tag parsing #496
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
Address tag parsing #496
Conversation
…int. No longer will consider any tag string containing a version as a candidate. Accordingly, default configuration no longer uses [vV] (some unit tests changed as a result) since most unit tests do no use the prefix.
There is a small issue (which is causing the test failure) that a tag without the prefix will fail to pass. Changing the regex from Thanks gain for the changes |
Merged into master via 50833b4 |
… intended with default TagPrefix of "[vV]|"
@JakeGinnivan, I committed another pass to better illustrate what I was trying to accomplish. The intent was to have the TagPrefix denote whether to treat as optional. This being the default should handle most legacy usages with the exception of those already carrying around the old default of "[vV]" in their GitVersionConfig.yaml. Technically, this would be a breaking change to those people. I apologize for having left loose ends with the failed test. I'm only reiterating because I feel the partial inclusion of the "[vV]|" is leaving the code base a little off (since the ? within the regex makes this redundant). |
I get you. The only issue is if someone has run Do you see an issue with leaving the default as |
Yes as merged it corrects my issue. It is only the remnants of what I was trying to accomplish that have left a bad taste in my mouth. I agree with the backwards compatibility issue. I will rework my pull tomorrow as a cleanup only. Thanks. |
Thanks, sorry I missed part of what you were doing |
…at resulted from a partial merge of pull request. More specifically TagPrefix is always considered optional.
@JakeGinnivan Here is the cleanup I promised. |
@Tungsten78 could you submit a PR for this? |
Opening PR to discuss changes highlighted in #495