Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow reverting slice lowercasing to the previous behavior #1576

Open
1 task done
sagikazarmark opened this issue Jun 29, 2023 · 0 comments · May be fixed by #1577
Open
1 task done

Allow reverting slice lowercasing to the previous behavior #1576

sagikazarmark opened this issue Jun 29, 2023 · 0 comments · May be fixed by #1577
Labels
kind/enhancement New feature or request
Milestone

Comments

@sagikazarmark
Copy link
Collaborator

Preflight Checklist

  • I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description

#1387 fixed a bug around how case insensitivity works in Viper. Unfortunately it causes issues for a number of key players in the field.

Proposed Solution

Allow reverting back to the previous behavior using a go tag. This is going to be a Viper v1 thing only.

Viper v2 will either be completely case insensitive or will allow partial case sensitivity.

Alternatives Considered

No response

Additional Information

No response

@sagikazarmark sagikazarmark added the kind/enhancement New feature or request label Jun 29, 2023
Repository owner deleted a comment from github-actions bot Jun 29, 2023
@sagikazarmark sagikazarmark added this to the v1.17.0 milestone Jun 29, 2023
@sagikazarmark sagikazarmark linked a pull request Jun 29, 2023 that will close this issue
@sagikazarmark sagikazarmark modified the milestones: v1.17.0, v1.18.0 Sep 11, 2023
@sagikazarmark sagikazarmark modified the milestones: v1.18.0, v1.19.0 Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant