raise an error when we encounter malformed yamls#28
Open
jianingy wants to merge 1 commit intoytoolshed:masterfrom
Open
raise an error when we encounter malformed yamls#28jianingy wants to merge 1 commit intoytoolshed:masterfrom
jianingy wants to merge 1 commit intoytoolshed:masterfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi,
This patch uses 'die' to report a malformed yaml error.
Well, I dont think use $self->error in _init is a good idea since Class.pm says that $self->error is used for handling method's error, for example,
When we are in _init context, return $self->error('error message') actually returns an undef that makes the object invisible to a caller and make it impossible to get $obj->{_error}.