You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After fully integrating the examples into this repo (see #43), and recommending a backwards-compatible approach for simplifying workflow configuration (see #49), it might make sense to provide wrappers (in their own namespaces) for workflows against commonly used/contributed services.
Open questions:
How supported will these be?
provide caveat in the ns docstring
Is there a good way to provide testing for them? (Does the service in question provide testing credentials for public use?)
Can a testing approach be integrated with TravisCI?
After fully integrating the examples into this repo (see #43), and recommending a backwards-compatible approach for simplifying workflow configuration (see #49), it might make sense to provide wrappers (in their own namespaces) for workflows against commonly used/contributed services.
Open questions:
ns
docstringPart of release #64
The text was updated successfully, but these errors were encountered: