Did you mean autosuggest somehow broken - Githubissues

thoughtbot / parity

Shell commands for development, staging, and production parity for Heroku apps

https://thoughtbot.com

MIT License

889 stars 57 forks source link

Did you mean autosuggest somehow broken #185

Closed iduuck closed 4 years ago

iduuck commented 4 years ago

Help us track down and resolve parity problems faster with this template.

What command did you execute?

staging deployu

What did you expect to happen?

I expected that the "Did you mean" engine, that it tells me: "Did you mean: deploy".

What actually happened?

Some information about your installation

What's your operating system?
What's the output of which development, which staging, which production? Parity has had multiple installation channels, and it's not uncommon for an old version to be somewhere else in your path.
If installed via Homebrew, what does brew list parity output?
If installed via Rubygems, what's the gem version?

geoffharcourt commented 4 years ago

Thanks for reporting!

The parity-specific commands (deploy, migrate, tail, etc.) aren't going to work with Heroku's autocomplete or did-you-mean correction. deploy isn't a Heroku command, and their CLI won't recognize it.

For us to handle this, we'd have to implement our own did-you-mean handler, and that seems like a prohibitively expensive undertaking and probably hard to do without requiring new gem dependencies.

If there's a straightforward PR that can fix this I'd be open to the change, but I don't think this is feasible unfortunately.