sureshjoshi
commented
6 months ago Not really sure what this would look like.
Would it take the place of filesystem? Or do we want a target "cue" (like a colon).
For example, most of the targets will look something like this, so we can trigger specifically off the colon at the end.
Alternatively, we do something like pants fmt :<tab> which kicks off the autocomplete
src/python/pants/engine/download_file_integration_test.py:tests
src/python/pants/engine/engine_aware.py
src/python/pants/engine/env_vars.py
src/python/pants/engine/environment.py
src/python/pants/engine/environment_test.py:tests
src/python/pants/engine/explorer.py
src/python/pants/engine/fs.py
src/python/pants/engine/fs_test.py:tests
...
tests/python/pants_test/pantsd/pantsd_integration_test.py:pantsd_integration
tests/python/pants_test/pantsd/pantsd_integration_test_base.py:pantsd_integration_test_base
tests/python/pants_test/pantsd/test_lock.py
tests/python/pants_test/pantsd/test_pants_daemon_core.py
tests/python/pants_test/pantsd/test_process_manager.py
tests/python/pants_test/pantsd/service:service
tests/python/pants_test/pantsd/service:tests
tests/python/pants_test/pantsd/service/__init__.py
tests/python/pants_test/pantsd/service/test_pants_service.py:tests
tests/python/pants_test/util:tests
tests/python/pants_test/util/test_requirements.py:tests
Right now, the shell completions are goal/options focused - it would be cool to trigger on targets as well