feat: add support for nested file paths in latch metadata #381
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
maximsmol
requested changes
Jan 25, 2024
ayushkamat
requested changes
Jan 25, 2024
…/nested-file-paths
ayushkamat
requested changes
Jan 26, 2024
ayushkamat
reviewed
Jan 27, 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.
The purpose of this is to support nested file paths in the
generate-metadatacommand.The interface is a bit more complicated; however, this allows users to be able to upload Snakemake workflows without having to make any modifications to their config.yaml (which can sometimes be quite large).
Not planning on merging until docs are updated.