Accept incorrectly insensitivised frontpage config keys #4237
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.
This is a fix to deal with the after effects of the bug that was fixed in #4128, specifically the incorrect saving of the
sortBy
andsavedFilterId
keys in the front page UI configuration. The viper update in #4107 thoroughly converts all keys in the config file to lowercase, so the UI will need to deal withsortby
andsavedfilterid
keys in existing systems.