refactor(query): move Dataset into query API#492
Merged
Conversation
|
Test Results 437 files 437 suites 20s ⏱️ Results for commit 3023f4d. ♻️ This comment has been updated with latest results. |
remiceres
changed the title
remiceres
approved these changes
Jul 16, 2026
remiceres
left a comment
remiceres
left a comment
Contributor
There was a problem hiding this comment.
Approved after review.
|
Author
|
thanks Remi |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move the public SPARQL Dataset type from core.next.storagemanager.api.dataset to core.next.query.api.dataset. Dataset represents query configuration (FROM / FROM NAMED), not storage behavior. This changes the public package, so consumers must update their imports.