Allow several Galaxy Markdown directives to be embedded. #19086
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.
First step toward implementing #17522.
Reserving a whole block of HTML makes sense for the display of an image or table but for some of the directives it is a bulky thing that really breaks up reports. These are things you'd want to use in legends or headers or footers or in explanatory text.
Here is a before and after demonstrating using the directive to not waste so much space describing the name and type of a dataset in a report.
The page content demonstrating the embedded Markdown syntax.
I've been planning this syntax for years and many of the directives that don't make a lot of sense on their own - links, names, types, etc... were designed with this in mind some day. The tool reports #19054 & #19067 have a bunch of obvious use cases things you'd want to include (and that would also make sense in a workflow) that would benefit from this work. Two being - the tool name and the tool parameter name or text. Rendering all that dynamically would keep the report and the XML in syntax automatically.
How to test the changes?
(Select all options that apply)
License