Fix migrate command version matchers #1769
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.
Issue #, if available:
N/A.
Description of changes:
Previously, Smithy models with versions without a decimal suffix (
.0
)would not be matched properly in the
smithy migrate
command.For Smithy models with a version of
"1"
, the upgraded files wouldresult in conflicting version control statements, e.g.
Similarly for Smithy models with a version of
"2"
, the files wouldincorrectly attempt to be upgraded, e.g.
This change loosens the version matchers to match the
Version::fromString
implementation.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.