feat: Show all available task with task list

[hoxbro]

Resolves #1276

TODO:

• Add test(s), Skipping it for now
• Add an example
• Update schema/model.py.
• Update reference/configuration.md

Maybe:

• Add --hidden flag so user can do it from the CLI.

Mainly copied over functionality from other places in the code.

[ruben-arts]

He @hoxbro, It works like a charm. The change in the list mechanism is ready for me.

The hidden field needs some more work, because it is a manifest change:

• Add a test to see that it is read correctly in rust.
• We always try to add manifest features to at least one of the examples/..
• The schema/model.py needs to know about it.
• It needs to be documented in the reference/configuration.md
• Nice to have would be that the pixi task add would get a --hidden flag so user can do it from the cli.

If that would take some time you could also move that to a different PR.

[hoxbro]

Add a test to see that it is read correctly in rust.

Can you help me and tell me which file(s) I should add the tests to?

We always try to add manifest features to at least one of the examples/..

What do you think about updating the polarify example with the following:

[tasks]
postinstall = "pip install --no-build-isolation --no-deps --disable-pip-version-check -e ."
python_version = {cmd = 'python --version --version', hidden = true}
polar_version = {cmd = 'python -c "import polars; print(f\"Polars version: {polars.__version__}\")"', hidden = true}
start = {depends_on=['python_version', 'polar_version']}
# Before:
# start = 'python -c "import sys; print(f\"Python version: {sys.version}\"); import polars; print(f\"Polars version: {polars.__version__}\")"'

The schema/model.py needs to know about it.

I have updated the model and the schema.json file (please correct me if I should not have done this).

It needs to be documented in the reference/configuration.md

This should now be done.

[hoxbro]

I have tried to add the CLI argument in https://github.com/prefix-dev/pixi/pull/1286/commits/b89a048acdf244ddca825146e46ecb841b4cb0f7/

[hoxbro]

I noticed that env would always be set as {} if cwd and now hidden were set. I updated the code so this is no longer the case in 28cfda. I don't think the code is the pretties, but it works.

[ruben-arts]

What do you think about updating the polarify example with the following:

Seeing this I was reminded of this issue: #934
Should this also be included in the hidden logic? To make it like fully hidden?

[ruben-arts]

Nice additions!

[ruben-arts]

The best way to test it in the rust code would be to put it in tests/task_tests.rs but I see that that would be a lot more work then the feature it self. So I think it's find to skip it for now.

[ruben-arts]

For the example, what about the cpp_sdl example where the configure could be hidden? There I could see users using it.

[hoxbro]

Should this also be included in the hidden logic? To make it like fully hidden?

I actually like seeing the commands, even though they are hidden. I don't think adding a silent command will be too hard, but if so, I or someone else can do it in another PR.

I will take a look at the cpp_sdl example later today.

[ruben-arts]

He @hoxbro, I'm really sorry to say this, but we're talking in a voice chat about this feature and @wolfv came with another option which made the logic even simpler, and more intuitive from a user perspective and we would like to change it to that.

Removing the hidden option but use _ in the task name to hide it from the task list.

This would reduce all the changes required to support this feature.

e.g.:

[tasks]
_hidden = "echo This task is not listed but can be run"
echo = {depends_on = ["_hidden"]}

> pixi task list
* echo

[hoxbro]

No problem. I will take a look at it later.

Do you also want then want this to be hidden from pixi info?

more intuitive from a user perspective

I think this statement is a bit of a stretch, as this is a hidden feature (pun intended 😄 ) and likely will be harder to discover except by looking at the documentation.

Also, make it a bit weird if you actually want to run the hidden feature.

[ruben-arts]

Do you also want then want this to be hidden from pixi info?

Yes please.

I think this statement is a bit of a stretch, as this is a hidden feature (pun intended 😄 ) and likely will be harder to discover except by looking at the documentation.

I agree that its a stretch as it is purely based on taste. However this feature not resulting in changed behavior of the actual task, which makes me like the small naming trick compared to a full option.

I hope this improve the explanation for the request for change.

[hoxbro]

I want to use filter_map here as this seems to be the correct thing to do. Just need some more time to get it right.

no spoilers 🙂

[hoxbro]

I'm not 100% sold on if filter_map is better than the filter and map combination.

[ruben-arts]

Looks great! One tip to consolidate the logic into one function.

[ruben-arts]

Awesome, Thanks!