Skip to content

Add preview feature warnings to documentation#6663

Merged
bentsherman merged 3 commits intomasterfrom
docs-preview-feature-warnings
Dec 17, 2025
Merged

Add preview feature warnings to documentation#6663
bentsherman merged 3 commits intomasterfrom
docs-preview-feature-warnings

Conversation

@pditommaso
Copy link
Member

Summary

  • Add warning admonitions to documentation pages for preview features (typed processes and workflow recursion)
  • Clarify that the syntax and behavior may change in future releases
  • Make preview warnings consistent across feature-flags.md

Files changed

  • docs/process-typed.md - Added warning + note admonitions
  • docs/workflow.md - Added warning + note for recursion section
  • docs/reference/process.md - Added warning + note for typed inputs/outputs section
  • docs/reference/feature-flags.md - Made preview warnings consistent

Test plan

  • Verify docs build correctly
  • Review warning/note formatting renders properly

🤖 Generated with Claude Code

Add warning admonitions to documentation pages for preview features
(typed processes and workflow recursion) to clarify that the syntax
and behavior may change in future releases.

Signed-off-by: Paolo Di Tommaso <paolo.ditommaso@gmail.com>
@pditommaso pditommaso requested a review from a team as a code owner December 16, 2025 10:37
@netlify
Copy link

netlify bot commented Dec 16, 2025

Deploy Preview for nextflow-docs-staging ready!

Name Link
🔨 Latest commit e76c3d7
🔍 Latest deploy log https://app.netlify.com/projects/nextflow-docs-staging/deploys/6942f61d79ecd000089b3580
😎 Deploy Preview https://deploy-preview-6663--nextflow-docs-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@christopher-hakkaart
Copy link
Collaborator

I'd prefer to limit sequential admonitions if possible. I've merged the two into a single note to address the preview feature requirements, and that they may change. We saw regular questions/errors being reported in Slack, so I think the more explicit we can be to advise developers the better.

@pditommaso
Copy link
Member Author

My primary concern is to be as much as possible explicit to provide more context for LLMs, and therefore better to be verbose and redundant than terse in order to reduce the risk to hallucinate the model

Signed-off-by: Ben Sherman <bentshermann@gmail.com>
@bentsherman bentsherman merged commit cdc7a58 into master Dec 17, 2025
25 checks passed
@bentsherman bentsherman deleted the docs-preview-feature-warnings branch December 17, 2025 18:42
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

Successfully merging this pull request may close these issues.

3 participants