Skip to content

Improve repr string representation of spatial types - #1231

Merged
robsdedude merged 1 commit into
neo4j:6.xfrom
robsdedude:feat/spatial-repr
Aug 22, 2025
Merged

Improve repr string representation of spatial types#1231
robsdedude merged 1 commit into
neo4j:6.xfrom
robsdedude:feat/spatial-repr

Conversation

@robsdedude

Copy link
Copy Markdown
Member

Instead of POINT(1.0 2.0 3.0) (regardless of the sub-type) the repr string representation is now WGS84Point(1.0, 2.0, 3.0) or similar.

This is more in line with Python's recommendations:

If at all possible, this should look like a valid Python expression that could be used to recreate an object with the same value (given an appropriate environment). If this is not possible, a string of the form <...some useful description...> should be returned.

-- https://docs.python.org/3/reference/datamodel.html#object.__repr__

@robsdedude
robsdedude marked this pull request as draft August 21, 2025 11:41
@robsdedude
robsdedude marked this pull request as ready for review August 21, 2025 13:21

@MaxAake MaxAake 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.

@robsdedude
robsdedude merged commit 54dc5db into neo4j:6.x Aug 22, 2025
24 checks passed
@robsdedude
robsdedude deleted the feat/spatial-repr branch August 22, 2025 13:57
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.

2 participants