Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DOC-666 Change "Accessing attributes" to "Accessing attributes in workflows" #5886

Open
wants to merge 1 commit into
base: master
from
Open

DOC-666 Change "Accessing attributes" to "Accessing attributes in workflows" #5886

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions docs/user_guide/data_types_and_io/accessing_attributes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,15 @@
(attribute_access)=

# Accessing attributes
# Accessing attributes in workflows

```{eval-rst}
.. tags:: Basic
```

You can directly access attributes on output promises for lists, dicts, dataclasses and combinations of these types in Flyte. This functionality facilitates the direct passing of output attributes within workflows,
enhancing the convenience of working with complex data structures.
You can directly access attributes on output promises for lists, dicts, dataclasses and combinations of these types in Flyte.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
You can directly access attributes on output promises for lists, dicts, dataclasses and combinations of these types in Flyte.
You can directly access attributes on output promises for lists, dictionaries, dataclasses, and combinations of these types in Flyte.

Note that while this functionality may appear to be the normal behavior of Python, code in `@workflow` functions is not actually Python, but rather a Python-like DSL that is compiled by Flyte.
Consequently, accessing attributes in this manner is, in fact, a specially implemented feature.
This functionality facilitates the direct passing of output attributes within workflows, enhancing the convenience of working with complex data structures.

```{note}
To clone and run the example code on this page, see the [Flytesnacks repo][flytesnacks].
Expand Down