-
Notifications
You must be signed in to change notification settings - Fork 5
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple minor style changes and comment changes. I haven't quite looked at the reflection code yet.
@@ -197,9 +204,7 @@ func (c *Client) renderStarlark(cfg []yaml.Resource) error { | |||
for _, resource := range cfg { | |||
switch t := resource.(type) { | |||
case *yaml.Pipeline: | |||
pipeline := resource.(*yaml.Pipeline) | |||
|
|||
sl.MarshalPipeline(pipeline) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My gut tells me that this could really return an error. Are there any places in this function where errors are being ignored or not returned?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I first wrote this, I had all the err:=
stuff in it. Then I eventually removed it because there was nothing that actually emitted an error.
5193024
to
ec5a31e
Compare
Co-authored-by: Kevin Minehart <kmineh0151@gmail.com>
Co-authored-by: Kevin Minehart <kmineh0151@gmail.com>
For Drone builds that are already using Starlark, being able to export a
Shipwright build as Starlark will allow the import of a Shipwright
build into the Starlark one, making possible a gradual transition from
one build tool to the other.