Skip to content

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

Open
@OrangeUtan

Description

@OrangeUtan

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions