Better logging in random_test.dart, and less overall noise from warnings #81
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.
Noticed that we never set
yamlWarningCallback
when parsing YAML internally, this meant that the terminal would show warnings.This is sad, because some of the internal stuff really only used
loadYamlNode
to determine if a string needed to be quoted, or if the edits were sane -- so warnings aren't actually intended for the end-user.One could argue that we should avoid edits that produce warnings, but that seems to an orthogonal concern, this really just stops warnings produces internally from polluting stdout.