Use a literal path for Nextclade data input #877
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
Replaces a reference to the _rule_ that produces Nextclade data needed for alignment with the _literal path_ to the corresponding output. This approach allows users to define custom rules that generate the same output and override the workflow's default rules. This kind of functionality is important, as it allows users to easily modify the workflow DAG from their custom build configuration and avoid maintaining a fork of the main workflow that can get outdated easily. Related to #875
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.
Description of proposed changes
Replaces a reference to the rule that produces Nextclade data needed for alignment with the literal path to the corresponding output. This approach allows users to define custom rules that generate the same output and override the workflow's default rules. This kind of functionality is important, as it allows users to easily modify the workflow DAG from their custom build configuration and avoid maintaining a fork of the main workflow that can get outdated easily.
Related issue(s)
Related to #875
Testing