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

Handle case where user accidentally uses Process() with a Config when… #109

Merged
merged 3 commits into from
May 16, 2024
Merged

Handle case where user accidentally uses Process() with a Config when… #109

merged 3 commits into from
May 16, 2024

Conversation

pdewilde
Copy link
Contributor

… they should use ProcessWith() by converting their call to the respective ProcessWith call.

resolves #108

… they should use ProcessWith() by converting their call to the respective ProcessWith call.
envconfig.go Show resolved Hide resolved
@sethvargo sethvargo enabled auto-merge (squash) May 16, 2024 21:13
@sethvargo sethvargo merged commit 61cfc0d into sethvargo:main May 16, 2024
1 check passed
@pdewilde pdewilde deleted the passthrough-process-with-config branch May 17, 2024 00:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature Request: Consider mitigating possiblity of calling Process with envconfig.Config as argument.
2 participants