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

Align Get* and Unmarshal behavior better #1744

Open
1 task done
sagikazarmark opened this issue Jan 30, 2024 · 0 comments
Open
1 task done

Align Get* and Unmarshal behavior better #1744

sagikazarmark opened this issue Jan 30, 2024 · 0 comments
Labels
kind/enhancement New feature or request

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

Different forms of reading from Viper often lead to different results due to different implementations.

For example:

Proposed Solution

Use a single implementation (mapstructure+decode hooks? UnmarshalKey?) for all forms of reading from Viper.

Chances are this would be a breaking change, so it either needs a feature flag or needs to be delayed to v2.

Alternatives Considered

No response

Additional Information

No response

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

No branches or pull requests

1 participant