chore: replace "coordinate" with "value" in XML doc comments and internal identifiers#235
Merged
petesramek merged 2 commits intoextend-polylinealgorithm-multi-dimensional-supportfrom Apr 13, 2026
Conversation
Agent-Logs-Url: https://github.com/petesramek/polyline-algorithm-csharp/sessions/a91e90b4-cfd4-4daa-8202-ce52524fb335 Co-authored-by: petesramek <2333452+petesramek@users.noreply.github.com>
…d tests Agent-Logs-Url: https://github.com/petesramek/polyline-algorithm-csharp/sessions/a91e90b4-cfd4-4daa-8202-ce52524fb335 Co-authored-by: petesramek <2333452+petesramek@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
petesramek
April 13, 2026 14:42
View session
petesramek
merged commit 7dc6aae
into
extend-polylinealgorithm-multi-dimensional-support
4 checks passed
petesramek
deleted the
copilot/update-xml-comments-and-replace-coordinate
branch
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
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.
The codebase still used "coordinate" terminology throughout XML doc comments and internal identifiers, despite the API having been refactored to the generic
TValueabstraction. This aligns all documentation and internal naming with the current design.XML doc comments (16 files)
geographic coordinate(s)→value(s)in<summary>,<typeparam>,<param>, and<returns>tags across all public and internal types (PolylineEncoder,PolylineDecoder,IPolylineEncoder,IPolylineDecoder,IPolylineFormatter,PolylineEncodingOptions,PolylineOptions,PolylineItemFactory,PolylineFormatter,FormatterBuilder,PolylineEncoderExtensions,PolylineEncoding,Defaults,ExceptionGuard,LogWarningExtensions,LogDebugExtensions)IPolylineEncoderfromCoordinatetoValuetype nameInternal identifiers
ThrowCoordinateValueOutOfRangeThrowValueOutOfRangeFormatCoordinateValueMustBeBetweenFormatValueMustBeBetweenDefaults.Coordinate(nested class)Defaults.ValuecoordinateIndex(log param)valueIndex"Decoded coordinate: ...""Decoded value: ...""Current coordinate is at index""Current value is at index"All renames are internal — no public API or method parameter names changed. Tests updated to match new identifiers and log message strings.