Conversation
Test Results1 263 files - 119 1 263 suites - 119 1h 23m 38s ⏱️ -2s For more details on these errors, see this check. Results for commit 2f6f831. ± Comparison against base commit 2a81ded. This pull request removes 1294 and adds 11 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
flow-server/src/main/java/com/vaadin/flow/component/geolocation/Geolocation.java
Outdated
Show resolved
Hide resolved
|
Provides access to the browser's Geolocation API with two usage modes: - get(): one-shot position request with success/error callbacks - track(): continuous tracking via a reactive Signal tied to a component's lifecycle, using a GeolocationState sealed type (Pending | GeolocationPosition | GeolocationError) that enables exhaustive pattern matching Includes records for coordinates, position, error, and options, a JS module that bridges navigator.geolocation to Vaadin's event system, and unit + integration tests.
|
There was a problem hiding this comment.
Would it make sense to convert this to TypeScript and move to flow-client?
There was a problem hiding this comment.
In addition, please make sure that TypeScript would have clear JSON event data definitions. This would help matching any changes with Java in future.



Wraps the browser's Geolocation API with two entry points:
Geolocation.get()for one-shot positionGeolocation.track()for continuous tracking via Signals, automatically tied to the owner component's lifecycle