Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sort command-block collected qza/qzv files #107

Closed
thermokarst opened this issue Feb 13, 2017 · 6 comments
Closed

Sort command-block collected qza/qzv files #107

thermokarst opened this issue Feb 13, 2017 · 6 comments

Comments

@thermokarst
Copy link
Contributor

thermokarst commented Feb 13, 2017

Current Behavior
It's a little confusing when the itemized list of outputs for a multi-command block aren't presented in the same order as the commands as executed.

References
screen shot 2017-02-12 at 7 22 48 pm

@jairideout
Copy link
Member

👍, this would be clearer than the sorted output. The directive doesn't parse the commands; it only collects the .qza/.qzv files that are created by a block, so it doesn't know what command(s) the files originated from. It might be solved by looking at the last modified timestamp of the files to determine order (we're looking at timestamps already to detect overwritten outputs).

A workaround for now is to split these commands out into separate command blocks.

@gregcaporaso
Copy link
Member

A workaround for now is to split these commands out into separate command blocks.

I was thinking that that might just be good practice anyway for this, so that's it's super clear for new users that the commands are independent of each other.

@jairideout
Copy link
Member

Sounds good! @gregcaporaso, do you think splitting the commands out is useful for the upcoming release? If so, I can create a separate issue and leave this one open for when we get around to fixing it.

@gregcaporaso
Copy link
Member

gregcaporaso commented Feb 21, 2017 via email

@jairideout
Copy link
Member

Sounds good. Thinking about it more, I created an issue to track this separately (sounds like we'd want both issues resolved at some point): #111

@cherman2
Copy link
Contributor

I am closing this because I think this was fixed. I went through some of our tutorials and was not able to find any occurrences. Please re-open if this issue is still occurring.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants