Closed general

fusion_sch_place_part ignores validateOnly and places the part

Glenn Jones · 4d ago ·closed by Colby Knox

What happens

fusion_sch_place_part with "validateOnly": true placed the part for real. The reply said mutated: true, and a follow-up fusion_sch_pins showed the part on the sheet at the requested spot.

fusion_sch_place_part {"expectDocument":"LEDster-Driver","sheet":1,"library":"LEDster_Driver","symbol":"CC0603KRX7R9BB104","designator":"C80","comment":"100nF 50V X7R","x":21500,"y":-400,"validateOnly":true,"reason":"..."}

Fusion bridge 1.13.84, Windows, cloud electronics design with a linked cloud library.

Expected

With validateOnly: true, check the library, symbol, designator and position and report what would happen, with mutated: false and nothing added. Fusion also adds the part to the board, so an unwanted placement has to be cleaned up on both the schematic and the board.

1 Reply

Colby Knox marked this in progress · 4d ago
Colby Knox · 4d ago

Thanks Glenn, fixed in Fusion bridge 1.13.85 (public now).

fusion_sch_place_part's check-only flag was named dryRun, so it didn't recognise validateOnly (the name fusion_schematic_run uses) and placed the part. Now validateOnly and dryRun mean the same thing on every verb:

  • fusion_sch_place_part with validateOnly: true checks the library, symbol, designator and position and answers mutated: false, dryRun: true. Nothing is added to the schematic or the board.
  • A verb that has no check-only mode now refuses either flag with dry_run_not_supported and does nothing, instead of running for real.

Checked live with your call's shape: both flags left the sheet and board unchanged.

Update with bridge_install, or it arrives on the next automatic update. If C80 from your test run is still on LEDster-Driver, delete it on the schematic and Fusion removes it from the board too.

Colby Knox closed this · 4d ago

Log in to reply.