mirror of
https://github.com/galaxyproject/galaxy.git
synced 2026-09-24 16:30:27 +08:00
John Chilton
4de71a0c82
The metadata system will then "sniff" the outputs and set the type appropriately.
Tool used to demonstrate and test this functionality is included, run the test with:
./run_tests.sh -framework -id output_auto_format
If auto_format="true" than explicitly setting ``format="another_type"`` will prevent the tool from loading so that we can allow this to specify a default type later without breaking backward compatiblity.
Update 1:
- Switched from ``format="auto"`` to ``auto_format="true"`` based on Dan's comments (https://github.com/galaxyproject/galaxy/pull/130).
Update 2:
- Updated this to work when setting metadata internally.
- Switch underlying representation of type from ``_auto_`` to ``_sniff_`` based on seeing a new block in ``galaxy.jobs``. ``auto`` indicates the tool should specify the datatype at runtime. This is in some ways the inverse of that (the tool telling Galaxy to detect the type instead of Galaxy telling the tool to) so I decided it would be best to not have ``auto`` and ``_auto_`` doing completely different things.
This directory contains tools only useful for testing and demonstrating aspects of the tool syntax. Run the test driver script 'run_tests.sh' with the '-framework' as first argument to run through these tests. Pass in an '-id' along with one of these tool ids to test a single tool. Some API tests use these tools to test various features of the API, tool, and workflow subsystems. Pass the argument '-with_framework_test_tools' to 'run_tests.sh' in addition to '-api' to ensure these tools get loaded during the testing process. Finally, to play around with these tools interactively - simply replace the 'galaxy.ini' option 'tool_config_file' with: tool_config_file = test/functional/tools/samples_tool_conf.xml