Repository navigation
Let the uri builder stay inside the route it was asked from - #21
Merged
Merged
Conversation
A resource the current route already stands at - its receiver, or the resource the receiver stands for (extraReceiver) - takes the rest of its uri from the route instead of the canonical tree. So far only AGBaseUriBuilder in apptive-base did this; the walk only uses HOP terms, so it belongs here. Whether a resource is in scope is asked of the uri space (isResource:inScopeOf:), defaulting to identity. A space whose objects can be database proxies overrides it there instead of HOP knowing about proxies. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
A resource the current route already stands at - its receiver, or the resource the receiver stands for (extraReceiver) - takes the rest of its uri from the route instead of the canonical tree. So far only AGBaseUriBuilder in apptive-base did this; the walk only uses HOP terms, so it belongs here.
Whether a resource is in scope is asked of the uri space (isResource:inScopeOf:), defaulting to identity. A space whose objects can be database proxies overrides it there instead of HOP knowing about proxies.