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

Update to Golang 1.15 #83

Merged
merged 6 commits into from
Oct 5, 2020
Merged

Update to Golang 1.15 #83

merged 6 commits into from
Oct 5, 2020

Conversation

gesellix
Copy link
Owner

@gesellix gesellix commented Oct 3, 2020

Relates to #80
Fixes #81

@gesellix gesellix changed the title Run CI on Golang 1.14 Update CI to use current Golang release Oct 3, 2020
@gesellix gesellix changed the title Update CI to use current Golang release Update to Golang 1.15 Oct 5, 2020
@gesellix gesellix merged commit 26f4611 into master Oct 5, 2020
@gesellix gesellix deleted the golang1.14 branch October 5, 2020 08:08
gesellix added a commit that referenced this pull request May 26, 2022
Other file formats like JSON or YAML would provide more type information, and unmarshalling would create correct types. Properties files aren't that useful, so we have to enforce some types by ourselves. We have to keep an eye on other types beside boolean, but this one seems sufficient for now.

Relates to urfave/cli#1376, which made our previous workaround (see #81 and #83) fail due to a private function in the InputSourceContext interface.
gesellix added a commit that referenced this pull request May 26, 2022
Other file formats like JSON or YAML would provide more type information, and unmarshalling would create correct types. Properties files aren't that useful, so we have to enforce some types by ourselves. We have to keep an eye on other types beside boolean, but this one seems sufficient for now.

Relates to urfave/cli#1376, which made our previous workaround (see #81 and #83) fail due to a private function in the InputSourceContext interface.
gesellix added a commit that referenced this pull request May 26, 2022
Other file formats like JSON or YAML would provide more type information, and unmarshalling would create correct types. Properties files aren't that useful, so we have to enforce some types by ourselves. We have to keep an eye on other types beside boolean, but this one seems sufficient for now.

Relates to urfave/cli#1376, which made our previous workaround (see #81 and #83) fail due to a private function in the InputSourceContext interface.
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.

Boolean values in ini file
1 participant