How to compose commands in env scripts

[kunaltyagi]

I want to use mypy-baseline to allow incremental adoption in the project. The usual way to do this is:

# 1st run
mypy <options> | mypy-baseline sync
# subsequent runs
mypy <options> | mypy-baseline filter

If I want to not repeat the mypy command in the scripts section, how can I accomplish the following with minimal duplication?

[tool.hatch.envs.lint.scripts]
typing = ['typing_all | mypy_baseline']  # <-- This is just not possible
typing_all = 'mypy --install-types --non-interactive {args:src/my_folder tests}'
mypy_baseline = 'mypy-baseline {args:filter} --baseline .mypy_baseline.txt'  # <-- how do 2 args behave?
typing_sync = ['typing_all | mypy_baseline sync']

[ofek]

https://hatch.pypa.io/latest/config/environment/overview/#scripts

[kunaltyagi]

I've read this section and it doesn't answer my questions:

1. How do I pipe other scripts (eg: typing_all) in some other script (eg: typing)?
2. Is it possible to separate command line args with in-config arguments? AFAIK, {args} seems to be replaced like a macro, copied to all instances of {args}

[ofek]

Oh you want piping, I thought you meant you wanted to chain them in a list. I'm not sure that is possible but I'm going to try in a few minutes.

Can you explain what you want regarding the arguments question?

[ofek]

This works for me.

❯ hatch run piping2
testing

[envs.default.scripts]
piping1 = 'echo testing'
piping2 = 'piping1 | python -c "import sys; print(sys.stdin.read().strip())"'

[kunaltyagi]

So, piping is working as expected. It was an issue with the tool. Created a PR with a note because there's no issue center: orsinium-labs/mypy-baseline#21

[kunaltyagi]

For the arguments, I was looking for separate arguments for separate parts of the command, somehow. I know it sounds bonkers but attempting incremental adoption in a project is PITA

[kunaltyagi]

So, I found this result. Looks really weird because piping seems to work for you