Register fully-qualified process names at compile-time #6312
Conversation
This file contains hidden or 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
✅ Deploy Preview for nextflow-docs-staging canceled.
|
christopher-hakkaart
approved these changes
Jul 24, 2025
bentsherman
force-pushed
the
fix-process-selector-warnings
branch
from
c704d58 to
c8a82e8
Compare
Signed-off-by: Ben Sherman <bentshermann@gmail.com>
bentsherman
force-pushed
the
fix-process-selector-warnings
branch
from
c8a82e8 to
6996f0b
Compare
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.
This PR extends the strict parser to resolve fully-qualified process names via static analysis -- including conditional processes.
This should eliminate any false warnings when validating process selectors. Thus we can deprecate the
nextflow.enable.configProcessNamesValidationfeature flag and move towards requiring all feature flags to be defined in the script.