Conversation
…d backup procedure of input file
Member
Author
|
I will ignore the security warning from codacy for the moment |
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
1 participant
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.
The shed_tool_conf.xml configuration file tends to become more and more complex over time and tool installations.
Thus
<section>with same attributes id and name (identity of submenus) are sparse in shed_tool_conf.xml which complicate the management of submenus in the Galaxy tool panel.This tool defragments the
<section>tags.Thus, after cleaning, each submenu in the Galaxy tool panel have a single
<section>in shed_tool_conf.xml whose<tool>children correspond to the tools hosted in this submenu.Note that the tools also backup the original shed_tool_conf.xml before xml manipulation.