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

[v2] Add support for optional fields for config struct #5828

Open
yurishkuro opened this issue Aug 11, 2024 · 5 comments
Open

[v2] Add support for optional fields for config struct #5828

yurishkuro opened this issue Aug 11, 2024 · 5 comments
Labels
area/otel good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement v2

Comments

@yurishkuro
Copy link
Member

Looking for a volunteer to add support for optional fields for config structs.

Objective: create a draft PR with a prototype solution outlined in go-viper/mapstructure#37 (make sure it's a draft to avoid creating notifications noise to go-viper maintainers). Update this ticket with a link so that we can collaborate on that prototype.

@yurishkuro yurishkuro added help wanted Features that maintainers are willing to accept but do not have cycles to implement good first issue Good for beginners v2 labels Aug 11, 2024
@dosubot dosubot bot added the area/otel label Aug 11, 2024
@nag0yan
Copy link

nag0yan commented Aug 12, 2024

@yurishkuro
Hello. Can I try this issue?

@yurishkuro
Copy link
Member Author

You don't need to ask

@mahadzaryab1
Copy link
Collaborator

@yurishkuro opened a draft at go-viper/mapstructure#42. Let me know if you have any feedback and I'd be happy to incorporate it in.

@akstron
Copy link
Contributor

akstron commented Oct 29, 2024

Hi @mahadzaryab1 I think this issue can be closed since your PR got merged?

@yurishkuro
Copy link
Member Author

issue is not solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/otel good first issue Good for beginners help wanted Features that maintainers are willing to accept but do not have cycles to implement v2
Projects
Status: No status
Development

No branches or pull requests

4 participants