fix(config/cors): use strings.Fields for string to string slice fields #1179
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.
@showwin pointed out that we regressed in terms of splitting behaviour on
allowed_origins
here:#1173
Before the config refactor, we were splitting using
strings.Fields()
(this was the internal behaviour ofviper.GetStringSlice()
). Afterwards,mapstructure.StringToSliceHook(",")
was leading to a simplestrings.Split(..., ",")
.This adjusts the string to slice hook to use
strings.Fields(...)
.This function treats one or more consecutive whitespace characters as a delimiter.
I added an example case to demonstrate this.
Once merged, we will cut a few patch releases on previous versions.