Skip to content

Generating completion scripts requires Swiftly to be initialized #360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SimplyDanny opened this issue May 18, 2025 · 1 comment
Open

Comments

@SimplyDanny
Copy link
Contributor

Running swiftly --generate-completion-script when Swiftly has not yet been initialized leads to:

Could not load swiftly's configuration file at /Users/brew/.swiftly/config.json.
  
To begin using swiftly you can install it: 'swiftly init'.

I feel initialization shouldn't be a requirement for shell completion to be generated. Is there a reason for that?

This is currently blocking the PR that tries to automate this task during installation with Homebrew.

@cmcgee1024
Copy link
Member

@SimplyDanny this flag should be added to the list of exclusions for requiring swiftly to be initialized. There's no reason why generating the command-line completions should require initialization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants