romshark / yamagiconf

98%

main: 98%

LAST BUILD ON BRANCH refs/tags/v0.6.1

branch: refs/tags/v0.6.1

CHANGE BRANCH

x

Reset

Sync Branches

• refs/tags/v0.6.1
• main
• refs/tags/v.0.10.3
• refs/tags/v0.1.0
• refs/tags/v0.10.0
• refs/tags/v0.10.1
• refs/tags/v0.10.10
• refs/tags/v0.10.2
• refs/tags/v0.10.4
• refs/tags/v0.10.5
• refs/tags/v0.10.6
• refs/tags/v0.10.7
• refs/tags/v0.10.8
• refs/tags/v0.10.9
• refs/tags/v0.2.0
• refs/tags/v0.2.1
• refs/tags/v0.2.2
• refs/tags/v0.3.0
• refs/tags/v0.4.0
• refs/tags/v0.5.0
• refs/tags/v0.5.1
• refs/tags/v0.5.2
• refs/tags/v0.5.3
• refs/tags/v0.6.0
• refs/tags/v0.7.0
• refs/tags/v0.8.0
• refs/tags/v0.9.0
• refs/tags/v1.0.0
• refs/tags/v1.0.1
• refs/tags/v1.0.2
• refs/tags/v1.0.3
• refs/tags/v1.0.4

Build # 9181924018

Build Type

push

github

Committed by romshark

Commit Message

fix: Error on env tag on yaml.Unmarshaler

Return an error for env tag on a field of a primitive named type
that implements the `yaml.Unmarshaler` interface because for a type
like `type MyString string` that implements `yaml.Unmarshaler`
env unmarshaling will just copy the env value to the underlying
string potentially bypassing any validation logic that might
have been defined in `UnmarshalYAML`. Therefore it's safer to use
`encoding.TextUnmarshaler` instead since it's supported by both
the env and the yaml parsers.

Run Details

3 of 3 new or added lines in 1 file covered. (100.0%)

623 of 635 relevant lines covered (98.11%)

121.56 hits per line