Fix: validate --custom-tax argument to prevent TypeError - #58
Merged
Conversation
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.
Fixes #57
Description:
This PR resolves a
TypeErrorthat occurs when running subcommands likemess downloadthat do not have the--custom-taxoption defined.The conditional check for
config.args.custom_taxinfunctions.smkandsetup.smkhas been updated from a simple truthiness test toisinstance(config.args.custom_tax, str).This change ensures the relevant code block is only entered when a user has actually provided a file path (a string). This makes the shared scripts robust and prevents them from failing when included in workflows with different sets of command-line arguments.