feat(client): add use_nextflow_pipelines flag to geometry creation#1929
Merged
feat(client): add use_nextflow_pipelines flag to geometry creation#1929
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
andrzej-krupka
force-pushed
the
andrzej/nextflow-geometry-flag
branch
from
95aae07 to
aaadb11
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
lei-flex
previously approved these changes
Mar 27, 2026
Expose the useNextflowPipelines flag in the Python client so users can opt into Nextflow-based geometry processing. The flag is passed through Geometry.from_file() -> GeometryDraft -> NewGeometryRequest -> POST /v2/geometries request body. Defaults to False -- no behavior change for existing users. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
lei-flex
force-pushed
the
andrzej/nextflow-geometry-flag
branch
from
aaadb11 to
68d2d61
Compare
use_nextflow_pipelines doesn't match the Pydantic field name use_nextflow, causing a ValidationError at runtime. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
lei-flex
approved these changes
Apr 1, 2026
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
3 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.
Expose the useNextflowPipelines flag in the Python client so users can opt into Nextflow-based geometry processing. The flag is passed through Geometry.from_file() -> GeometryDraft -> NewGeometryRequest -> POST /v2/geometries request body.
Defaults to False -- no behavior change for existing users.
Note
Low Risk
Low risk: adds an optional flag that defaults to
Falseand only affects the request payload when explicitly enabled.Overview
Adds an opt-in
use_nextflow_pipelinesflag to geometry creation so callers can route geometry processing through the Nextflow pipeline.The flag is stored on
GeometryDraft, surfaced onGeometry.from_file(), and serialized intoNewGeometryRequestasuseNextflowin thePOST /v2/geometriesrequest body; thefrom_file()factory is adjusted to constructGeometryDraftdirectly to carry this new parameter.Written by Cursor Bugbot for commit 9631074. This will update automatically on new commits. Configure here.