-
Notifications
You must be signed in to change notification settings - Fork 5
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
envPrefix is not supported #2
Comments
@emmanuelay hi, the complex structure parsing is not implemented yet, I'm going to fix it soon |
Great, thanks! Really nice work btw! |
Add `envPrefix` tag support for struct fields. Fix: #2
Add `envPrefix` tag support for struct fields. Fix: #2
Thanks for reporting, now it should be fixed, you can check examples with |
Wonderful! Thank you very much @g4s8 ! |
Render nested structures annotated with `envPrefix` as sublists of origin field, using documentation from the origin field as a text for this sublist. Ref: #2
Render nested structures annotated with `envPrefix` as sublists of origin field, using documentation from the origin field as a text for this sublist. Ref: #2
Render nested structures annotated with `envPrefix` as sublists of origin field, using documentation from the origin field as a text for this sublist. Ref: #2
Render nested structures annotated with `envPrefix` as sublists of origin field, using documentation from the origin field as a text for this sublist. Ref: #2
Fix panic when parsing an empty doc string in anonymous structure field. Ref: #2
I use caarlos0/env for my REST API project. The package has support for
envPrefix
which looks like this:..which should result in:
DB_PORT
as an environment variable.But instead it renders an markdown with a header, and nothing else.
Is this expected behavior or am I doing something wrong?
The text was updated successfully, but these errors were encountered: