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

Documentation for private/hidden tasks is ambiguous #173

Closed
sean-abbott opened this issue Apr 20, 2017 · 2 comments
Closed

Documentation for private/hidden tasks is ambiguous #173

sean-abbott opened this issue Apr 20, 2017 · 2 comments

Comments

@sean-abbott
Copy link

sean-abbott commented Apr 20, 2017

Without experimentation, it's not clear if private hidden tasks with a name that starts with underscore mean that you should do _task_private_task() or task__private_task() or something else entirely.

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
@sean-abbott
Copy link
Author

In case anyone is curious, you can either use task__private_task() or in the return dictionary, you can have a basename key, 'basename': '_private_task'

@schettino72
Copy link
Member

well, it is no ambiguous to me. The name of task is what comes after task_.

Anyway it would be nice to have an example in the docs...
Would you please submit a pull-request to the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants