Update guidelines for strict parser#7134
Merged
Merged
Conversation
✅ Deploy Preview for nextflow-docs-staging canceled.
|
christopher-hakkaart
approved these changes
May 12, 2026
Collaborator
christopher-hakkaart
left a comment
christopher-hakkaart
left a comment
There was a problem hiding this comment.
Docs look good.
Optionally, we could also add more warnings about migrating to 26.4 strict parser and setting nextflow.syntax = 'v1' as a workaround.
christopher-hakkaart
approved these changes
May 12, 2026
Collaborator
christopher-hakkaart
left a comment
christopher-hakkaart
left a comment
There was a problem hiding this comment.
Docs look good.
Optionally, we could also add more warnings about migrating to 26.4 strict parser and setting nextflow.syntax = 'v1' as a workaround.
bentsherman
force-pushed
the
docs-strict-parser
branch
2 times, most recently
from
6ba2ffc to
28712d9
Compare
Signed-off-by: Ben Sherman <bentshermann@gmail.com>
bentsherman
force-pushed
the
docs-strict-parser
branch
from
28712d9 to
effeb3b
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 updates the "Preparing for strict syntax" page to reflect the current state of Nextflow 26.04 (strict parser enabled by default)
Remove uses of "strict syntax" where possible in favor of "strict parser" or just "Nextflow", to reflect the fact that the strict parser is a strict implementation of Nextflow, not a new language or syntax version
Add a section on legacy CLI type casting with suggested workarounds
Fix inconsistencies in other related syntax guidelines
Add linter warnings that were missing