google / go-jsonnet

44%

master: 44%

LAST BUILD ON BRANCH yaml-doc-stream

branch: yaml-doc-stream

CHANGE BRANCH

x

Reset

• yaml-doc-stream
• add-clamp-to-linter
• bazelfixes
• bazelisk
• bugfix/setuptools-72
• build_cleanup
• ci-check-bzlversions
• ci/python-linux-aarch64-wheels
• dependabot/go_modules/go_modules-e86e96fb2e
• digitsep
• error-test-for-manifestYamlDoc
• feat/csv
• feat/is-null
• fix-issue-679
• fix-linter-manifest-json-ex
• fix-linter-multiple-snippets
• fix-manifestYamlDoc-error-check
• fix-minArray-maxArray-keyF
• fix-negative-range
• fix-parse-yaml
• fix/manifest-maxstack-bypass
• fix_807_removeAt
• fmt-bug-809
• go-mod-version
• golang-archive-names
• limit-bitwise-range
• master
• mcarl/fix-oob-formatter
• no-libjsonnet-h
• optional-symlinks
• output-newline
• patch-1
• prepare-release
• print-fmt-names
• python-release-gil
• pywheels
• readme-updates
• remove-key
• restrict-writes
• rudo-fix-comprehension-over-string-error-message
• rudo.thomas/fix-cached-import-syntax-error
• security-doc
• smoke
• table-test-number
• update-ci
• update-cpp-jsonnet
• update-cpp-script
• update-dependencies
• update-go-deps
• update-project-status
• use-local-test-overrides
• v0.10.0
• v0.16.0
• v0.17.0
• yihao/bazel-example

Build # 22822294901

Build Type

Pull #862

github

Committed by johnbartholomew

Commit Message

improve handling of YAML document streams in std.parseYaml

This doesn't make them fully correct, in particular directives sections
(e.g., "%YAML 1.2" directive before a document start marker) are not
handled correctly, but they weren't handled correctly before, either.

It also doesn't recognise or try to do anything about document end
markers (`...`).

This fix does allow scalar documents to be on the same line as the
document start tag which is valid per examples in the YAML spec,
see for example https://yaml.org/spec/1.2.1/#id2760844
(YAML 1.2.1 spec, section 2.3 Scalars)

It also matches the C++ jsonnet output for std.parseYaml("42\n---"),
which is a stream of two documents, a scalar and then an empty document
(where the empty document is interpreted as JSON null)

Pull Request Pull Request #862: Improve handling of YAML document streams in std.parseYaml

Run Details

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

6067 of 13806 relevant lines covered (43.94%)

1421.84 hits per line