Minor style nits affecting YAML output #798
Merged
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.
Changes
Address some minor styling nits affecting YAML output.
omitempty
for string, slice, map or pointer fields that can be omitted.omitempty
from non-pointer struct fields, whereomitempty
doesn't do anything.From
encoding/json
:In addition to this change, some fields that are structs could be changed to pointers, to allow them to be omitted from YAML output as well, when not specified.
For example,
TaskRunSpec
'sOutputs
field is anOutputs
struct, which means the field is always present in YAML output, but isoutputs: {}
when none are specified. If the field was a*Outputs
withjson:"outputs,omitempty
, it could be omitted from YAML if none are specified. Same withTaskRunSpec
'sInputs
andTrigger
fields, and some inPipelineRunSpec
, etc.It's possible that
outputs: {}
is preferrable to just omitting it, but it's unclear whether that was an explicit decision or not. 🤷♂️Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide
for more details.
Release Notes
N/A