feat(semver): Add support for build metadata #3126
Merged
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.
Overview
Currently the build metadata is parsed but is not printed out in any form. A semver which is parsed will not be identical to
the printed output:
Additionally, once set, there is no way to alter the metadata on the SemVer instance without formatting into a new string and re-parsing:
Therefore this PR attempts to address these two issues with the following APIs:
.format()
function which contains a single fieldstyle
. The style will dictate the format of the output of the function, it will not affect the format internal mutated fieldsthis.version
orthis.raw
, to preserve backwards compatibility and not require an extensive refactor..increment()
function will now have a new, optional,metadata: string
parameter which will set thethis.build
field with the new metadata or reset it to empty. Incrementing with no build data will not retain the previous build metadata.Related To
Notes
this.version
andthis.raw
fields are preserved as they were since those fields can be part of the comparison calculations. The only modifications are to the output of the format function.