Skip to content
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

Command "Beet: build" runs even though selected config file no longer exists #3

Open
OrangeUtan opened this issue Jun 29, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@OrangeUtan
Copy link
Collaborator

The build command uses the selected config file to execute beet.
However, it is still executed when that file doesn't exist, resulting in an error in the build task.

Instead of blindly executing the build command, checking if it exists would allow for more quality of live improvements:

  • Notify the user that the selected config file doesn't exist anymore
  • Open dialog to allow the user to choose a different config file
@OrangeUtan OrangeUtan added the enhancement New feature or request label Jun 29, 2021
@vberlier
Copy link
Member

Nice idea 👍

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

No branches or pull requests

2 participants