Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encoding of adjacency directionality through use of start and end leads to complex queries #627

Open
mbaudis opened this issue Jan 17, 2025 · 0 comments

Comments

@mbaudis
Copy link
Member

mbaudis commented Jan 17, 2025

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... )

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

No branches or pull requests

1 participant