You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The encoding of adjacency directionality through use of start and end named parameters makes queries complex. It requires that one knows the direction of the fusion partners or creates some complex $or requests.
From the point of querying it would be cleaner to have directionality agnostic base parameters and then an optional parameter for direction (which - for queries - won't be used much in practice).
(I'm personally not sure if I find the indication of a location solely through an end parameter really elegant or rather odd... )
The text was updated successfully, but these errors were encountered:
The encoding of adjacency directionality through use of
start
andend
named parameters makes queries complex. It requires that one knows the direction of the fusion partners or creates some complex$or
requests.From the point of querying it would be cleaner to have directionality agnostic base parameters and then an optional parameter for direction (which - for queries - won't be used much in practice).
(I'm personally not sure if I find the indication of a location solely through an
end
parameter really elegant or rather odd... )The text was updated successfully, but these errors were encountered: