Skip to content
This repository was archived by the owner on Feb 6, 2024. It is now read-only.

Support resolving YAML streams in Go resolver #444

Merged
merged 1 commit into from
Oct 17, 2019

Conversation

smukherj1
Copy link
Contributor

This fixes #443

@smukherj1
Copy link
Contributor Author

Relevant for #433

@k8s-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nlopezgi, smukherj1

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Comment on lines +56 to +64
testCases := []struct {
name string
// yamlDocs is a string with one or more YAML documents.
yamlDocs string
// want is the list of strings the YAML walker should visit.
want []string
// wantDocs is the number of docs the resolver should have operated on.
wantDocs int
}{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if it's a valid scenario, but can we have an empty yaml file? If so, can we have a test for that too?

- val1
- val2
---
---
- val3
- val4

@rbe-toolchains-pr-bot rbe-toolchains-pr-bot merged commit 0e86910 into bazelbuild:master Oct 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Regression: go resolver does not retain multiple documents found in an yaml file
5 participants