chore: add descriptions to env structures #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request improves the documentation and schema annotations for environment variable wrapper types across the codebase, making the intent and usage of these fields clearer for both developers and tools that consume the schema. Additionally, it disables the
llllinter in the GolangCI configuration.The most important changes are:
Schema annotation and documentation improvements:
descriptionfields to theValueandVariablestruct tags for all environment wrapper types (such asEnvAny,EnvString,EnvInt,EnvBool,EnvFloat,EnvMapString,EnvMapInt,EnvMapFloat,EnvMapBool,EnvStringSlice,EnvIntSlice,EnvFloatSlice,EnvBoolSlice). These descriptions clarify thatValueis the default literal if the environment variable is empty, andVariableis the environment variable to be evaluated. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]Linting configuration:
lll(line length linter) in.golangci.ymlto allow longer lines, which are now required due to the more descriptive struct tags.