You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issue tracker for an issue that matches the one I want to file, without success.
Problem Description
It is possible to create custom pflags by implementing the Value interface. The problem is that viper just calls ValueString() on value types it doesn't know about.
I implemented a custom StringToBool flag, which pflags unfortunately lacks. In order for this to work properly, I would need Viper to call a conversion function as is, e.g., done for stringToInt.
Proposed Solution
My suggestion would be to add an option to register custom conversion functions for value types.
A maintainer will take a look at your issue shortly. 👀
In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.
📣 If you've already given us your feedback, you can still help by spreading the news,
either by sharing the above link or telling people about this on Twitter:
Preflight Checklist
Problem Description
It is possible to create custom pflags by implementing the Value interface. The problem is that viper just calls ValueString() on value types it doesn't know about.
I implemented a custom
StringToBool
flag, which pflags unfortunately lacks. In order for this to work properly, I would need Viper to call a conversion function as is, e.g., done for stringToInt.Proposed Solution
My suggestion would be to add an option to register custom conversion functions for value types.
If a function is registered for a value type, Viper would then call this function in the find method.
I would offer to work on this if there is interest.
Alternatives Considered
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: