Open
Conversation
Added flag for allowing user to output directly into dest_path, without creating additional subdirectories.
Owner
|
Nice to have, but maybe we should also expose it to CLI. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added the option to output directly to the dest_path instead of creating a bundle_path on top of it.
In the spirit of giving the user a bit more control of where the FLACs end up. For instance, my use case is running deflacue as part of a pipeline. Currently, I call defaclue, then do a recursive glob for the output flacs as they are 3 subdirectories deep from where the dest_path is specified.
Perhaps a bit of a clutter-y solution and not as vital as the other bugfix, but wanted to put it here to discuss.