Detect nested stage-scripts and indent output accordingly
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the StagedScript implementation and tracing how stage headings are emitted when one script invokes another. Done means nested StagedScript output is visibly indented while top-level output remains unchanged; the issue names no files or tests to run.
Written by the indexing model from the issue text.
Description
It'd be really nice if a StagedScript could detect whether it was being run within the stage of another StagedScript, and, if so, adjust it's output by prepending an indent level. I have no idea how I might implement such a thing at the moment, but seeing the output of one script run by another is confusing for the user, because they just see all the stages consolidated together into a flat level, which can be misleading. E.g., consider just the stage headings in the output:
Opening project...
Building documentation...
Creating an environment... # This is a nested script,
Installing documentation dependencies... # but the user is unaware,
Building documentation... # Didn't we already do this above? # because the output doesn't say.
Building toolbox...
Cleaning up...
- Dominant language
- Python
- Stars
- 23
- Forks
- 2
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sandialabs/staged-script
-
Quick Type: Refactor
Difficulty 3/5 1-2 days Newbie friendliness 35/100
sandialabs/staged-script#300 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
sandialabs/staged-script#139 ·
-
Add Trilinos build scriptMay be free again @jmgate claimed this 775 days ago, and no pull request is open. OpenType: Documentation
sandialabs/staged-script#98 · 1 comment · 1 assignee ·
-
Save script execution summaryMay be free again @jmgate claimed this 775 days ago, and no pull request is open. OpenType: Feature
sandialabs/staged-script#97 · 1 assignee ·
-
Add stage summary info to the script execution summaryMay be free again @jmgate claimed this 780 days ago, and no pull request is open. OpenType: Feature
sandialabs/staged-script#93 · 1 assignee ·
All issues in sandialabs/staged-script
Similar issues
-
bug P2 rust
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jscott3201/rusty-bacnet#2085 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
evarness-ai/iris-harness#401 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
sistemicorp/scripts#62 ·
-
area/mac help wanted needs-qa
Difficulty 1/5 Under an hour Newbie friendliness 76/100