feat: add wt step eval for template expression evaluation#1004
Draft
feat: add wt step eval for template expression evaluation#1004
wt step eval for template expression evaluation#1004Conversation
…ntal)
Evaluates a minijinja template in the current worktree context and prints
the result to stdout. Reuses the existing hook template infrastructure
(variables, filters like hash_port/sanitize/sanitize_db).
Designed for scripting — no shell escaping, no decoration, output to
stdout only.
```
$ wt step eval '{{ branch | hash_port }}'
16066
$ curl http://localhost:$(wt step eval '{{ branch | hash_port }}')/health
```
Ref #947
Co-Authored-By: Claude <noreply@anthropic.com>
6 tasks
Owner
Author
|
Follow-up PR for per-branch kv state: #1006
|
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.
Summary
wt step evalsubcommand that evaluates a minijinja template in the current worktree context and prints the result to stdoutbranch,repo,worktree_path, etc.) and filters (hash_port,sanitize,sanitize_db) are availableThis is the first step from the IDEAS.md design doc, directly addressing the user request in #947 — "found no way to run it on a single branch."
Test plan
Ref #947