CapnSpek commented on PR #994: URL: https://github.com/apache/age/pull/994#issuecomment-1595178499
@rafsun42 the issue only arose when I noticed the ambiguity in the position of edge in the documentation, regarding which I created an issue here https://github.com/apache/age-website/issues/143 Then after discovering the odd behaviour I created the issue #870 In which I and John discussed how the original purpose of having orderability was "orderability was chosen over comparability in order to allow for the sorting, grouping, of output." Based on this information, I extrapolated the currently present priority order (which did not include edge or path at all btw) From Object, Vertex, Array String, Bool, Numbers, Null To Object, (Path, Edge), Vertex, Array, String, Bool, Numbers, Null. I reached on this decision because if the aim was orderability and grouping, then, it correctly orders types as:- Objects, Collection of graph elements (path), Graph elements (edges and vertices), Array, String, Bool, Numbers, Null. Because it only adds some priorities in between the previously defined priorities, and does not change the structure that previously was there, this change is backwards compatible, and fixes the bug adequately by defining the previously left ambiguous priorities. I'll come up with regression tests soon. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
