You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, SemanticVersion has the methods increaseMajor(), increaseMinor() and increasePatch(). The current implementation increments the specific version part, but it does not reset the following parts to zero.
While this is okay as long as it's documented accordingly, it might not be useful this way. Maybe these methods should be replaced by nextMajor(), nextMinor() and nextPatch methods.
While this might be more clear, it's still discussable what happens to the pre-release and the build part when using those methods.
For that reason, it might be better to not include neither of the mentioned methods in the initial release but rather add them later, depending on requirements and feedback.
The text was updated successfully, but these errors were encountered:
Currently,
SemanticVersion
has the methodsincreaseMajor()
,increaseMinor()
andincreasePatch()
. The current implementation increments the specific version part, but it does not reset the following parts to zero.While this is okay as long as it's documented accordingly, it might not be useful this way. Maybe these methods should be replaced by
nextMajor()
,nextMinor()
andnextPatch
methods.While this might be more clear, it's still discussable what happens to the pre-release and the build part when using those methods.
For that reason, it might be better to not include neither of the mentioned methods in the initial release but rather add them later, depending on requirements and feedback.
The text was updated successfully, but these errors were encountered: