-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Docs tweaks and a squashed bug #225
Conversation
has been exceeded </li> | ||
<li> `SKIP` will skip the task and possibly propogate the skip state through the | ||
flow, depending on whether downstream tasks have `skip_on_upstream_skip=True`. </li></ul> | ||
</li></ul> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok so this is up for debate; I put HTML directly into the docstring here so the list would format inside the table. I'm happy to remove this change though if we don't think it's appropriate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this particular case I think it's appropriate to favor the docs because it's such an important method, and if that means HTML I'm all for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was my thought too, awesome
has been exceeded </li> | ||
<li> `SKIP` will skip the task and possibly propogate the skip state through the | ||
flow, depending on whether downstream tasks have `skip_on_upstream_skip=True`. </li></ul> | ||
</li></ul> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this particular case I think it's appropriate to favor the docs because it's such an important method, and if that means HTML I'm all for it.
Closes #155
Check out the netlify deploy build to see it in action!