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.

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

"Save result" is misleading #288

Closed
christophfriedrich opened this issue Oct 22, 2021 · 1 comment · Fixed by #289
Closed

"Save result" is misleading #288

christophfriedrich opened this issue Oct 22, 2021 · 1 comment · Fixed by #289
Assignees
Milestone

Comments

@christophfriedrich
Copy link

The summary of save_result is "Save processed data to storage". This can be misleading to users who start synchronous jobs to "just have a look": They don't actually want to save something, especially not to storage -- they just want to output it.

Considering the above use case of "just a look", it's not obvious that you always need this process to actually get results from any process graph.

Looking back it might've been smarter to call this process something like output, but I guess for changing the name (especially of such a central process) it's a bit too late now :D

@m-mohr m-mohr self-assigned this Oct 22, 2021
@m-mohr m-mohr added this to the 1.2.0 milestone Oct 22, 2021
@m-mohr
Copy link
Member

m-mohr commented Oct 22, 2021

Indeed, I'll try to generalize this to also work better with sync. jobs and also web services.

m-mohr added a commit that referenced this issue Oct 25, 2021
m-mohr added a commit that referenced this issue Oct 25, 2021
@m-mohr m-mohr linked a pull request Oct 25, 2021 that will close this issue
m-mohr added a commit that referenced this issue Nov 4, 2021
@m-mohr m-mohr closed this as completed Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants