Skip to content

fix: allow precise probe coordinates - #1832

Open
loglapa wants to merge 3 commits into
grafana:mainfrom
loglapa:fix-434-coordinate-precision
Open

fix: allow precise probe coordinates#1832
loglapa wants to merge 3 commits into
grafana:mainfrom
loglapa:fix-434-coordinate-precision

Conversation

@loglapa

@loglapa loglapa commented Aug 25, 2026

Copy link
Copy Markdown

What this changes

  • allow latitude and longitude values with arbitrary decimal precision in the probe editor
  • preserve the existing coordinate bounds and validation behavior
  • cover six-decimal-place coordinates with a focused regression test

Testing

  • yarn test src/components/ProbeEditor/ProbeEditor.test.tsx --runInBand (14 tests)
  • yarn typecheck
  • yarn lint
  • git diff --check

All project commands were run in Docker.

Fixes #434

@github-actions

github-actions Bot commented Aug 25, 2026

Copy link
Copy Markdown

Signed commits report

All 3 commits between main and fix-434-coordinate-precision have verified signatures. ✅

@cla-assistant

cla-assistant Bot commented Aug 25, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@loglapa
loglapa force-pushed the fix-434-coordinate-precision branch from ac52379 to ccfdffe Compare August 25, 2026 17:19
@loglapa
loglapa marked this pull request as ready for review August 25, 2026 17:25
@loglapa
loglapa requested a review from a team as a code owner August 25, 2026 17:25
@loglapa
loglapa requested review from VikaCep and g3john August 25, 2026 17:25
@loglapa
loglapa force-pushed the fix-434-coordinate-precision branch from ccfdffe to 3215447 Compare August 25, 2026 18:50
Comment thread src/components/ProbeEditor/ProbeEditor.tsx Outdated
Signed-off-by: Vladislav Lapin <51929896+loglapa@users.noreply.github.com>
@loglapa
loglapa force-pushed the fix-434-coordinate-precision branch from 3215447 to be25815 Compare August 26, 2026 16:50
@loglapa

loglapa commented Aug 27, 2026

Copy link
Copy Markdown
Author

The requested coordinate precision change is addressed in be25815: both latitude and longitude inputs now use an explicit 0.000001 step instead of step="any", with regression coverage for the six-decimal contract. Focused tests, typecheck, and ESLint pass; Bugbot and the available GitHub checks are green. @g3john ready for re-review.

@loglapa
loglapa requested a review from g3john September 3, 2026 20:06

@g3john g3john left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM! Thank you

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.

lat/long doesn't accept google's number of significant digits?

2 participants