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

Lupl/ordering feature #227

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from
Draft

Lupl/ordering feature #227

wants to merge 9 commits into from

Conversation

lu-pl
Copy link
Contributor

@lu-pl lu-pl commented Feb 27, 2025

Closes #171 .

@lu-pl lu-pl force-pushed the lupl/ordering-feature branch 2 times, most recently from bf6a3e0 to 7a61bcb Compare February 28, 2025 12:47
lu-pl added 2 commits March 3, 2025 12:05
The specific type annotation 'type[_TModelInstance]' in
model_utils.model_traverse is not correct for recursive code paths;
the broader annotation 'type[BaseModel]' is more more appropriate.
@lu-pl lu-pl force-pushed the lupl/ordering-feature branch 3 times, most recently from ce33622 to 242059c Compare March 4, 2025 12:14
lu-pl added 7 commits March 5, 2025 16:52
sparql_utils.add_solution_modifier previously added the SPARQL
variable marker "?"; this however does not allow to pass ASC/DESC modifiers.

The change generalizes the add_solution_modifier templating and
requires SPARQL variables to be passed with a variable marker.

Also, the respective unit tests are adapted.
@lu-pl lu-pl force-pushed the lupl/ordering-feature branch from 242059c to 4bc0606 Compare March 5, 2025 15:54
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.

Implement ordering of results (default order and through QueryParameters argument)
1 participant