The latest version sections used a single hash, the level of the
document title; they now use the same level as the older entries.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Ensure history requests correctly include the access path part and prevent null pointer exceptions when adding the polymorphic query parameter in instance queries.
Matches the Context.fullPath -> path rename in information-system-model
and resource-registry-api.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Update type reading methods documentation in the client interface, refactor recursive child type collection to use a stable breadth-first traversal order with deduplication in the implementation, and add comprehensive unit tests for type read operations.
Update queryTypes implementation to wrap unexpected exceptions in
ResourceRegistryException rather than RuntimeException, improve javadoc
documentation, and add focused transport contract tests for type queries.
Implement request options context handling to support per-request configuration, custom headers, and response metadata within the Resource Registry client.
Update javadoc examples for `runQueryTemplate` to prefix parameter keys with `$` to align with expected query template parameter formatting, and handle null jsonNode values in `ResourceRegistryClientImpl`.
Rename `getTypeTreeNode` to `getTypeDagNode` and update related imports
to reflect the transition from tree structures to directed acyclic graphs
(DAGs) within the resource registry client.
Update ModelKnowledge generic type and method references to use
SchemaTypeInformation instead of TypeInformation to improve naming
clarity and consistency with the domain model.
Replace fully qualified class names with imported class references in Javadoc comments across the client implementation to improve readability and maintainability.
Clarify that context retrieval is restricted to the self-inclusive subtree of the token Context and update authorization requirements to reflect the scope-based access model.
Refactor the unmarshalling process in getInstances to explicitly declare the list type and scope the @SuppressWarnings annotation to the specific assignment, improving code clarity and type safety.
- update `jsonQuery` to use `QUERY` method via `X-HTTP-Method-Override`
- add `queryContexts`, `queryTypes`, and `queryQueryTemplates` for JSON query endpoints
- add depth-based `getContext` methods to support recursive subtree retrieval
- add `getContextHistory` methods for context history tracking
- remove legacy prepared-query methods: `getResourcesFromReferenceFacet`, `getFilteredResources`, `getRelatedResourcesFromReferenceResource`, and `getRelatedResources`
BREAKING CHANGE: removed legacy prepared-query methods that targeted the deprecated `GET /access/query/{resource-type}/{relation-type}/{reference-type}` endpoint.
- Upgrade gcube-bom to 4.1.0-SNAPSHOT
- Remove explicit version declarations for managed dependencies in pom.xml
- Update CHANGELOG.md with recent feature and refactoring changes
Update ResourceRegistryClientImpl and ResourceRegistryClientTest to use
the more accurate terminology 'FullPath' instead of 'FullName' for
context identification.
Remove the `rawQuery` methods and associated documentation and tests as they are no longer supported in the ResourceRegistryClient interface and implementation.
Introduce an overloaded `getTypeFromServer` method that accepts a depth parameter for more granular control over polymorphic type expansion. Deprecate the existing boolean-based `getTypeFromServer` method in favor of this new implementation.
Luca Frosini