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
api entrypoint to bypass context-parser #201
Labels
enhancement
new features
type: core
core functionality
up next
features that are more or less on the TODO list
Projects
Comments
yaythomas
added
enhancement
new features
up next
features that are more or less on the TODO list
type: core
core functionality
labels
Oct 31, 2020
yaythomas
added a commit
that referenced
this issue
Oct 31, 2020
yaythomas
added a commit
that referenced
this issue
Nov 7, 2020
yaythomas
added a commit
that referenced
this issue
Nov 9, 2020
yaythomas
added a commit
that referenced
this issue
Nov 12, 2020
yaythomas
added a commit
that referenced
this issue
Nov 12, 2020
yaythomas
added a commit
that referenced
this issue
Nov 12, 2020
yaythomas
added a commit
that referenced
this issue
Nov 12, 2020
yaythomas
added a commit
that referenced
this issue
Nov 12, 2020
yaythomas
added a commit
that referenced
this issue
Nov 12, 2020
yaythomas
added a commit
that referenced
this issue
Nov 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
new features
type: core
core functionality
up next
features that are more or less on the TODO list
API consumers want to invoke a pipeline without necessarily using the
main()
entry-point which assumes cli-esque shlex-ed args as input. Currently this means they have to drill further into the call-chain to invoke using a dict or context object directly, which are more internals than strictly speaking the api client should need to care about.Add new api entrypoint that allows:
Keep all existing entrypoints for backwards compatibility.
The text was updated successfully, but these errors were encountered: