[feat] harnesses can accept cli args#122
Merged
OwenPriceSkelly merged 10 commits intomainfrom Jan 9, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #49
Before, harnesses must have been zero-argument functions:
But a common pattern in some of the typical target use-cases (i.e. "monster scripts" that are run and re-run on a remote cluster) is to make heavy use of CLI args. We now support the following:
We don't do any of the signature inspection or parsing ourselves; since typer is already a dependency of ours, we just turn the
harnessinto an ad-hoc typer app with a single command at runtime. This adds a little unavoidable complexity (we need toinvoke_harness_with_argsinstead of just callingresult = harness_func()), but since we're ultimately just plugging into the very battle-tested typer/click libraries I'm not worried.As a bonus, power-users can also directly use
typer.Optionortyper.Arguments in theirharnessesand it should "just work" the same as it would a vanilla typer app.