Skip to content

Conversation

@piotrkluba
Copy link
Collaborator

@piotrkluba piotrkluba commented Feb 12, 2026

Note

Medium Risk
Changes the mesher JSON schema for Snappy edge refinements by introducing a new field, which could affect downstream mesher behavior or compatibility if not supported.

Overview
Adds a new geometric_test_only boolean to snappy.SurfaceEdgeRefinement to allow ignoring region edges and performing only geometric edge tests.

Updates Snappy surface meshing translation to always emit edges.geometricTestOnly (as "yes"/"no") in the generated mesher JSON, and refreshes translator fixtures/golden JSON plus tests to cover the new option.

Written by Cursor Bugbot for commit 496d025. This will update automatically on new commits. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

edges["minLen"] = refinement.min_len.value.item()
if refinement.retain_on_smoothing is not None:
edges["retainOnSmoothing"] = refinement.retain_on_smoothing
edges["geometricTestOnly"] = "yes" if refinement.geometric_test_only else "no"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent boolean format for geometricTestOnly field

Medium Severity

geometricTestOnly is serialized as a string "yes"/"no", while every other boolean field in the same edges dictionary (e.g., retainOnSmoothing) and elsewhere in the snappy translator output (e.g., multiRegionFeatureSnap, strictRegionSnap) uses a native JSON boolean (true/false). This inconsistency likely means the downstream consumer will receive an unexpected type for this field, potentially causing it to be ignored or misinterpreted.

Fix in Cursor Fix in Web

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.

1 participant