Fix precedence of commandline options and yaml options #181
Conversation
This file contains 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
natefoo
approved these changes
Sep 23, 2021
commandline options should take precedence over options specied in yaml file, but default values should be used if options are not set in yaml file. Fixes galaxyproject#180
mvdbeek
force-pushed
the
fix_option_parsing_and_tool_id_handling
branch
from
6f968e2
to
62ff309
Compare
|
This looks like an issue with bioblend? |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
commandline options should take precedence over options specied in yaml
file, but default values should be used if options are not set in yaml
file. Fixes #180