Tab autocomplete of application name no longer working

[Mahoney]

Heroku Version 8.0.2-25b54fa

macOs 13.2.1 (Ventura) M1

Installed via Homebrew, updated via heroku update.

I have run heroku autocomplete since updating.

What is the current behavior?

When an app called example-app exists, and is the only app the user has that starts with exa, typing heroku config -a exa and pressing tab does nothing (get an error bell)

What is the expected behavior?

When an app called example-app exists, and is the only app the user has that starts with exa, typing heroku config -a exa and pressing tab should complete the command to heroku config -a example-app

Typing heroku config -a and pressing tab does list all the apps.

[k80bowman]

Thank you so much for letting us know! We'll take a look.

GUS item

[cody-elhard]

On further review it seems to work for

heroku pg:backups:download -a ...

but NOT for

heroku run bash -a ...

[Mahoney]

Agreed - also does not work with heroku config -a <prefix>, though a simple heroku config -a does offer up all the apps.

[cody-elhard]

Fixed for me.

heroku -v
#=> heroku/8.1.7 darwin-x64 node-v16.19.0

[Mahoney]

Not for me:
heroku config -a + tab gives completions live-app-1, live-app-2, live-app-3.
heroku config -a live- + tab gives no completions.

~$ heroku -v 
heroku/8.1.7 darwin-x64 node-v16.19.0

[petrsigut]

The same for me:

heroku/8.1.9 darwin-x64 node-v16.19.0

[stof]

This is solved in 8.2.0

[Mahoney]

Not solved in heroku/8.4.1 darwin-arm64 node-v16.19.0

Ran heroku autocomplete --refresh-cache

I have multiple apps prefixed with live-

If I type heroku config -a live- and hit tab I get nothing.

[robotfelix]

After experiencing the same issue for years I asked an agent to try debugging the problem, and the good news is the fix is simple!

cli/src/commands/autocomplete/options.ts

Line 137 in 3e4c838

cacheCompletion = this.findCompletion(cacheKey, id)

cli/src/commands/autocomplete/options.ts

Line 149 in 3e4c838

cacheCompletion = this.findCompletion(cacheKey, id)

The two calls to findCompletion in cli/src/commands/autocomplete/options.ts are passing the arguments as (cacheKey, id), but the order of the arguments should have been swapped around as part of a refactor in 2018.

I've submitted PR #3686 to fix the problem