Inline elements in markdown reports

[mvdbeek]

It would be pretty neat if some things could be specified as inline elements.
In particular this would be history_dataset_as_image, but other elements might also be useful (galaxy version, galaxy url, name of dataset, workflow license). Markdown uses ![alt text](image_url "optional title") for images, I'm not sure what a galaxy version of that should look like. For text-like values we essentially just want to template strings, so maybe {{ the parameter }} might be ok ?

[mvdbeek]

As an example here's what we could do with this, that would be a high priority change for the VGP project

Image 1	Image 2
Caption 1	Caption 2

[jmchilton]

#19086

[mvdbeek]

That looks great! Anything we can do to get this over the finish line ?

[jmchilton]

#19086 doesn't implement allowing images in tables like that - but I guess we could turn ${galaxy history_dataset_as_image(blah)} into a native Markdown image pretty easily and then we wouldn't need anything special on the frontend besides potentially filling the correct GALAXY_ROOT like we do for other markdown (i.e. https://github.com/galaxyproject/galaxy/blob/dev/client/src/components/Tool/ToolHelpMarkdown.vue#L31).

As for anything to do, I'll offer you another sample sheet PR trade 😓. If you merge the Sample Sheet PR before the pyupgrade PR - I will set aside two days next week for the embedded Markdown work - one for fixing up the PR and the other for implementing the images.

[jmchilton]

I've implemented embedded history_dataset_as_image directives using the implementation outlined in my previous comment in #19086. It seems to work, I'll pull it out of draft when I get the CI a little less red. I keep hoping someone smarter than me about HTML concerns will do something about image display properties (width, height, etc...) but I'm not sure what that would look like. I would hope this approach could leverage whatever we do for that - seems feasible.

---

---