alexander-haller
commented
8 months ago In GitLab by @mhxion on Feb 14, 2024, 18:42
After some quick tests, I think I know why. This turns out to be much of larger issue stemming from some unrefactored code in src/elapi/configuration/config.py.
- The bash/zsh script for elapi auto-completion calls
elapi --help. - Which calls the CLI interface APIs (provided by a third-party library
typerwhich also provides the auto-completion bash/zsh script) fromsrc/elapi/cli/elapi.py. - Which in turn calls some essential configuration variables (like
APP_NAME== "elapi") fromsrc/elapi/configuration/config.py. config.pyprints any critical error message (if those errors exist) to STDERR as a priority before continuing with anything else.- Thus, the error messages are shown anytime the command
elapiis invoked in any way!
The best solution would be to refactor config.py such that the error messages aren't really printed anytime elapi command is run. config.py also requires refactoring to allow for elapi plugins to make use of elapi.yml, e.g., if a third-party developer writing an elapi plugin (and any script using the elapi package would be a valid elapi plugin!) wants to add their own key: value in elapi.yml. Doing the latter would solve this bug as well. However, that would take some work that maybe we can set to do at a later time.
In GitLab by @mhxion on Feb 14, 2024, 18:13
Reported by @alexander-haller.
When pressing
TABfor auto-completion, elapi also shows any unresolved error message along with the suggestions for auto-completions.This is also reproducible on iTerm on MacOS which suggests this isn't necessarily a terminal issue.