You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description
The "Exporting Data" tutorial correctly provides the input artifacts needed to run the example export commands, but labels them as "Output artifacts". This is the case for both examples given in the tutorial. The tutorial does not provide output file(s)/folders (which of course would not be artifacts for these commands).
Expected behavior
Input artifacts are labeled as such rather than as "Output artifacts". In a perfect world, output file(s)/folders are provided so users can see what the export commands actually produce.
Screenshots
Example of unexpected labeling:
Comments
I suspect this is in some way due to the automated document processing used to generate the tutorial pages, so perhaps it cannot actually be fixed, but I thought it was worth noting.
The text was updated successfully, but these errors were encountered:
Thanks for noticing and sharing that @AmandaBirmingham! This is an issue with our docs build. As we're transitioning how we manage the user docs, and phasing this site out in favor of https://use.qiime2.org, we're not going to fix for this release but rather just make sure that we don't introduce the same issue in the new docs.
Bug Description
The "Exporting Data" tutorial correctly provides the input artifacts needed to run the example export commands, but labels them as "Output artifacts". This is the case for both examples given in the tutorial. The tutorial does not provide output file(s)/folders (which of course would not be artifacts for these commands).
Expected behavior
Input artifacts are labeled as such rather than as "Output artifacts". In a perfect world, output file(s)/folders are provided so users can see what the export commands actually produce.
Screenshots
Example of unexpected labeling:
Comments
I suspect this is in some way due to the automated document processing used to generate the tutorial pages, so perhaps it cannot actually be fixed, but I thought it was worth noting.
The text was updated successfully, but these errors were encountered: