This repository has been archived by the owner on Oct 15, 2024. It is now read-only.
strict config parsing #204
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bjoernhaeuser
approved these changes
Jun 20, 2018
octopusx
approved these changes
Jun 20, 2018
svenwltr
added
the
kind/enhancement
svenwltr
force-pushed
the
strict-config-parsing
branch
from
16d58ff to
50be9f3
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Strict unmarshaling means, that the decoder will exit with an error, if a field does not exist in the struct. This would prevent unnoticed typos in the config.
@rebuy-de/prp-aws-nuke Please review.