Document collapsing boxes in reports/pages in an FAQ #4790
Merged
Conversation
This file contains 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
hexylena
changed the title
|
galaxyproject/galaxy#15260 galaxyproject/galaxy#16681 more are documented here in images |
shiltemann
approved these changes
Mar 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
also found out that if you want to use three backticks in a block, you have to use 4 in the parent block. And if you want 4, you guessed it, use 5.
markdown parsing is a literal unending nightmare. We hardcode looking for 3 backticks in places like the admin tutorial extraction, so, that's fun. Maybe need to switch to a real markdown engine eventually to fix that.
q: does it get filed as a Report faq or a Pages faq? More people probably use reports than pages but they're the same underlying thing.