Aglet

Prioritize Decimal Parsing Defects in Imports

Numeric separator defects matter most when a plausible but incorrect magnitude is accepted. A visible rejection may be easier to recover from than a clean-looking value changed by several orders of magnitude. Rank the consequence in the affected workflow and preserve uncertainty about inputs whose intended convention is unknown.

Decide where the work belongs

  1. Measure the semantic difference

    For known examples, compare the expected and saved values with their units. Record whether the issue changes magnitude, fractional precision, or only presentation. Identify calculations and decisions that use the field, without assuming every displayed formatting difference changes the underlying numeric value or downstream outcome.

  2. Group by producer convention

    Compare exports using decimal commas, decimal periods, and grouping separators. Identify the actual producers and field types involved. Estimate reach from relevant import attempts rather than language alone; a user’s interface locale does not necessarily match the convention used by a third-party export or source system.

  3. Assess detection before commitment

    Check whether the preview makes the interpreted magnitude visible and allows a supported format choice. Try the correction path using the original source string. Include reconciliation cost when an already accepted value cannot be distinguished from a genuinely large number without revisiting the source file.

What to carry forward

Record priority with confirmed numeric change, affected workflows, producer reach, and recovery effort. Escalate silent magnitude changes ahead of purely presentational differences when their consequences justify it. Assign a review trigger for another convention or evidence that the current warning fails to expose an ambiguous interpretation.

Technical background: Google Cloud documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow