Page MenuHomeElementl

Warn on @pipeline function returning value
ClosedPublic

Authored by schrockn on Oct 23 2020, 5:41 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Jul 2, 7:12 AM
Unknown Object (File)
Thu, Jun 30, 2:35 AM
Unknown Object (File)
Mon, Jun 27, 1:18 AM
Unknown Object (File)
Sun, Jun 26, 9:24 AM
Unknown Object (File)
Sat, Jun 25, 6:40 AM
Unknown Object (File)
Fri, Jun 24, 9:56 AM
Unknown Object (File)
Mon, Jun 13, 2:08 AM
Unknown Object (File)
Mon, Jun 6, 12:48 AM
Subscribers
None

Details

Summary

This is a precondition for the @pipeline @composite_solid
merging. Previously we were ignoring return values from @pipeline. However
as embeddable artifacts with outputs those return values will have meaning
and it will break existing code. Plan will be:

  1. Warn on @pipeline returning something and
  2. Special case behavior on the @pipeline decorator until we decide to break

people who have returned this.

This also converts pipelines in dagster and dagster-graphql to respect this
warning.

Test Plan

BK

Diff Detail

Repository
R1 dagster
Lint
Lint Not Applicable
Unit
Tests Not Applicable