internal/keyvaluetags: Allow KeyValueTags type passthrough in New(), add unit testing, and fix potential panic #19011
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.
Community Note
Reference: #18726 (comment)
The current behavior is to return an empty
KeyValueTags
if the type is unrecognized inNew()
in preference over panicking or requiring all consumers to implement error handling. This augmentsNew()
to accept the namedKeyValueTags
in addition to its underlyingmap[string]*TagData
type, preventing confusing behavior on an otherwise easy to miss resource/service implementation detail.Added unit testing to cover various
New()
type scenarios. Fixed panic discovered while implementing the unit testing.