|
63 | 63 | from dbt.artifacts.resources import SqlOperation as SqlOperationResource |
64 | 64 | from dbt.artifacts.resources import TimeSpine |
65 | 65 | from dbt.artifacts.resources import UnitTestDefinition as UnitTestDefinitionResource |
| 66 | +from dbt.artifacts.resources.types import FunctionType |
66 | 67 | from dbt.artifacts.schemas.batch_results import BatchResults |
67 | 68 | from dbt.clients.jinja_static import statically_extract_has_name_this |
68 | 69 | from dbt.contracts.graph.model_config import UnitTestNodeConfig |
@@ -1722,18 +1723,19 @@ class ParsedNodePatch(ParsedPatch): |
1722 | 1723 | freshness: Optional[ModelFreshness] = None |
1723 | 1724 |
|
1724 | 1725 |
|
1725 | | -# TODO: Maybe this shouldn't be a subclass of ParsedNodePatch, but ParsedPatch instead |
1726 | | -# Currently, `functions` have the fields like `columns`, `access`, `version`, and etc, |
1727 | | -# but they don't actually do anything. If we remove those properties from FunctionNode, |
1728 | | -# we can remove this class and use ParsedPatch instead. |
1729 | 1726 | @dataclass |
1730 | 1727 | class ParsedFunctionPatchRequired: |
1731 | 1728 | return_type: FunctionReturnType |
1732 | 1729 |
|
1733 | 1730 |
|
| 1731 | +# TODO: Maybe this shouldn't be a subclass of ParsedNodePatch, but ParsedPatch instead |
| 1732 | +# Currently, `functions` have the fields like `columns`, `access`, `version`, and etc, |
| 1733 | +# but they don't actually do anything. If we remove those properties from FunctionNode, |
| 1734 | +# we can remove this class and use ParsedPatch instead. |
1734 | 1735 | @dataclass |
1735 | 1736 | class ParsedFunctionPatch(ParsedNodePatch, ParsedFunctionPatchRequired): |
1736 | 1737 | arguments: List[FunctionArgument] = field(default_factory=list) |
| 1738 | + type: FunctionType = FunctionType.Scalar |
1737 | 1739 |
|
1738 | 1740 |
|
1739 | 1741 | @dataclass |
|
0 commit comments