Docs(Geolocator.ReportInterval): Clarify zero unsupported; 1 is minimum valid value #2506
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prmerger-automator
bot
added
do-not-merge
aschoorl
approved these changes
Sep 10, 2025
|
@GrantMeStrength I am from the Microsoft Geolocation team, and we made this change based on an internal bug report to clarify the documented behavior. Please merge this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an Important note to Geolocator.ReportInterval remarks:
Doc-only clarification aligned with product behavior; no code changes.
I work on the Windows Geolocation area; this reflects actual runtime behavior and avoids confusion when apps set 0.