David López
David López
This is a very WIP, but I wanted to get some feedback to see if this is going in the right direction or I'm completely off-road here. ## What did...
I was looking into ways of integrating the rich `planemo lint` results into the Galaxy Tools VSCode extension in a similar way as [the planemo tests](https://github.com/galaxyproject/galaxy-language-server/pull/110). I found in the...
This PR unifies the workflow invocation export UI while providing an easy way of defining new export formats. Every format can be downloaded or written to a remote source by...
Backport of #18052 to release 23.2 ## License - [x] I agree to license these and all my past contributions to the core galaxy codebase under the [MIT license](https://opensource.org/licenses/MIT).
Currently, when listing contents in a remote file source, we retrieve all possible files and directories inside, then perform client-side pagination and search. While this approach is enough for small...
Fixes #17960 WIP ## How to test the changes? (Select all options that apply) - [ ] I've included appropriate [automated tests](https://docs.galaxyproject.org/en/latest/dev/writing_tests.html). - [ ] This is a refactoring of...
This can be a custom command to detect and automatically remove those attributes which value is the same as the default. For example: ```xml ``` will be automatically reduced to:...
The current validation of the tool documents is based on the [Galaxy XML Schema Definition](https://github.com/galaxyproject/galaxy/tree/dev/lib/galaxy/tool_util/xsd). There are some validation rules that are interesting to have to better comply with the...
It would be nice to have the ability to see the tool UI rendered beside the code as you made some tweaks with the parameters, the help, etc. as @hexylena...
It would be helpful to have some more detail on how the `tests` and the `command` section is automatically generated and add it to the readme or wiki. Ref #105