feat(client): add use_nextflow_pipelines flag to geometry creation#1929
Open
andrzej-krupka wants to merge 2 commits intomainfrom
Open
feat(client): add use_nextflow_pipelines flag to geometry creation#1929andrzej-krupka wants to merge 2 commits intomainfrom
andrzej-krupka wants to merge 2 commits intomainfrom
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.
| parent_folder_id=self.folder.id if self.folder else "ROOT.FLOW360", | ||
| length_unit=self.length_unit, | ||
| description=description, | ||
| use_nextflow_pipelines=self.use_nextflow_pipelines, |
There was a problem hiding this comment.
Field name mismatch: use_nextflow_pipelines vs use_nextflow
High Severity
The NewGeometryRequest model defines the field as use_nextflow, but _create_project_root_resource passes it as use_nextflow_pipelines=self.use_nextflow_pipelines. Since use_nextflow_pipelines matches neither the field name (use_nextflow) nor its alias (useNextflow), Pydantic will raise a validation error at runtime whenever a user tries to create a geometry with this flag.
Additional Locations (1)
lei-flex
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
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.
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
Medium Risk
Medium risk because it changes the client-side request payload for geometry creation and adds a new public parameter; incorrect wiring of the flag could silently be ignored or alter processing behavior.
Overview
Adds a new
use_nextflow_pipelinesoption toGeometry.from_file()/GeometryDraftand attempts to forward it into thePOST /v2/geometriesrequest so users can opt into Nextflow-based geometry processing.Extends the
NewGeometryRequestmodel with auseNextflowboolean (defaultFalse) to carry this routing choice in the API payload.Written by Cursor Bugbot for commit 68d2d61. This will update automatically on new commits. Configure here.