Parent testing issue: #1
Source defect report: https://github.com/eviltester/anywaydata-ai-testing/blob/main/docs/testing/20260625/issue-230-001/defects/AD-003-commerce-price-direct-help-params-ignored.md
Testing artifact folder: https://github.com/eviltester/anywaydata-ai-testing/tree/main/docs/testing/20260625/issue-230-001
Original grid-table-editor story: eviltester/grid-table-editor#230
Original grid-table-editor PR: eviltester/grid-table-editor#247
The detailed defect report from the testing artifact is copied below.
AD-003: Directly typed commerce.price help-style params are ignored while params-dialog values work
Severity: Low/Medium
Status: confirmed suspicious behavior; params dialog path works, direct params-field path does not appear equivalent.
Environment
Steps to Reproduce
- Select
commerce.price from the method picker.
- Use the help example syntax in the params field:
(dec=2, max=20, min=10, symbol="$").
- Generate several rows.
- Repeat by opening the params dialog and entering
dec=2, max=20, min=10, symbol=$ in the separate fields.
Expected Result
The help-style params syntax and the params dialog should serialize to equivalent generation behavior, or the UI should clearly direct users to the params dialog and reject unsupported manual syntax.
Actual Result
The direct help-style params path generated values outside the requested 10-20 range and omitted the $ symbol, for example 35.69, 426.99, 280.05, 489.35.
The params dialog path generated expected values such as $16.55, $18.09, $19.05, $17.75, all within the configured range and with the symbol.
Notes
This may be a row params parsing issue rather than a method picker component issue, but the new Method Help Display shows params examples prominently and users may copy them into the row params field.
Parent testing issue: #1
Source defect report: https://github.com/eviltester/anywaydata-ai-testing/blob/main/docs/testing/20260625/issue-230-001/defects/AD-003-commerce-price-direct-help-params-ignored.md
Testing artifact folder: https://github.com/eviltester/anywaydata-ai-testing/tree/main/docs/testing/20260625/issue-230-001
Original grid-table-editor story: eviltester/grid-table-editor#230
Original grid-table-editor PR: eviltester/grid-table-editor#247
The detailed defect report from the testing artifact is copied below.
AD-003: Directly typed commerce.price help-style params are ignored while params-dialog values work
Severity: Low/Medium
Status: confirmed suspicious behavior; params dialog path works, direct params-field path does not appear equivalent.
Environment
codex/230-method-picker-mvc/04570e0e428d../support/command-coverage-valid-params-rerun.json,../support/loop2-focused-rechecks.json../screenshots/loop2-commerce-price-params-dialog.pngSteps to Reproduce
commerce.pricefrom the method picker.(dec=2, max=20, min=10, symbol="$").dec=2,max=20,min=10,symbol=$in the separate fields.Expected Result
The help-style params syntax and the params dialog should serialize to equivalent generation behavior, or the UI should clearly direct users to the params dialog and reject unsupported manual syntax.
Actual Result
The direct help-style params path generated values outside the requested 10-20 range and omitted the
$symbol, for example35.69,426.99,280.05,489.35.The params dialog path generated expected values such as
$16.55,$18.09,$19.05,$17.75, all within the configured range and with the symbol.Notes
This may be a row params parsing issue rather than a method picker component issue, but the new Method Help Display shows params examples prominently and users may copy them into the row params field.