[tools/shoestring]: Shortened command and subcommand autocompletion

[ccHarvestasya]

Problem

• Running the tool requires prefixing with python3 -m
• No autocomplete support for subcommands

Solution

• Define Poetry scripts to eliminate the need for python3 -m
• Enable subcommand autocompletion using argcomplete

This is not something I use frequently, but it’s a nice-to-have improvement.

[codecov]

Codecov Report

Attention: Patch coverage is 75.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 99.21%. Comparing base (c028861) to head (dfe6e29).

Files with missing lines	Patch %	Lines
tools/shoestring/shoestring/__main__.py	80.00%	1 Missing ⚠️
tools/shoestring/shoestring/wizard/__main__.py	66.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1439      +/-   ##
==========================================
+ Coverage   98.28%   99.21%   +0.93%     
==========================================
  Files         164      159       -5     
  Lines        6770     6642     -128     
  Branches      143      143              
==========================================
- Hits         6654     6590      -64     
+ Misses        116       52      -64     

Flag	Coverage Δ
explorer-rest	?
tools-shoestring	99.37% <75.00%> (+2.33%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
tools/shoestring/shoestring/__main__.py	97.82% <80.00%> (+0.20%)	⬆️
tools/shoestring/shoestring/wizard/__main__.py	91.52% <66.66%> (+91.52%)	⬆️

... and 6 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Wayonb]

Can you add tests for this?

[ccHarvestasya]

It is possible to run tests that go through each entry point, so I’ve added them.
However, these are just tests that pass through the entry points.
Do you think it would be better to include some assertions?

[Wayonb]

Thanks. Those tests are fine.
Initially, I was thinking of installing a Shoestring(pip install -e .) to verify that the shoestring command runs.

[Wayonb]

This seems to only work with a specific shell? 🤔
You’re using bash or zsh as your shell

[ccHarvestasya]

1. It needs to be executable simply as shoestring.
   (This has already been addressed via tool.poetry.scripts.)

2. To enable autocompletion, you need to run eval "$(register-python-argcomplete shoestring)" (or add it to your .bashrc to enable it permanently).

Since an extra command is required, it ends up feeling like a hidden feature 😅

[Wayonb]

1. Yes, but I was wondering if argcomplete only supports bash or zsh shell

2. Yes, will need to update the README on how to enable autocompletion

[ccHarvestasya]

1. It looks like argcomplete only supports Bash and Zsh.
   Are there any other shells we should consider supporting? For example, PowerShell?
   If you have suggestions for other shells worth supporting, let me know — I’ll look into whether we can support them.

2. I'll add instructions for enabling autocomplete to the README later.

[Wayonb]

1. Adding the list of supported shells to the README is sufficient.

[ccHarvestasya]

OK, I'll add it to the README later.