Update to 2.8.6 - RC2 - #2014
Merged
Merged
Conversation
requested organization - derive top_level_root from the current organization, its parent, or its grandparent when is_top_level_root is enabled - return minimal related organization metadata containing UUID, short_name, and long_name - keep related organizations within single-organization responses - collect and deduplicate related organizations at the top level of paginated organization responses - preserve the existing legacy organization response path - omit reports_to and top_level_root when no corresponding relationship can be resolved - add BaseOrg UUID and oversees indexes for hierarchy lookups - add an idempotent migration for existing database deployments - document the UUID-based top_level_root and related organization response fields - cover direct and two-level ROOT reporting relationships - add unit coverage for paginated related organization deduplication
Add a Secretariat-only GET /api/registry/org-hierarchy endpoint that returns the complete, unpaginated organization forest. Project each node to short_name, long_name, and children. Build hierarchy responses from one lightweight organization query. Construct parent and child maps in JavaScript so traversal remains linear, supports arbitrary depth, and avoids repeated database reads. Handle standalone organizations, missing references, duplicate edges, multiple parents, self-references, and cycles defensively. Add _hierarchy to GET /api/registry/org/:identifier. Return the path from the top-level Root to the requested organization while excluding sibling branches from its ancestors. Include the requested organization's complete descendant subtree. Remove _relatedOrganizations from registry organization list and detail responses, along with the additional aggregation lookup used to hydrate it. Continue using _userMap for expanded user and conversation-author metadata. Add recursive JSON schemas and OpenAPI documentation for the hierarchy endpoint and embedded _hierarchy response. Expose the standalone hierarchy response schema through the schemas controller. Expand development population data to exactly 1,000 organizations. Add two top-level Roots with four child Roots each, assign four CNAs directly to each top-level Root, and distribute the remaining CNA organizations across the child Roots. Keep the Secretariat and sister_20 organizations standalone. Add unit and integration coverage for hierarchy projection, trimming, access control, schema validation, deep traversal, malformed relationships, organization renames, subtree moves, and populated seed distribution. BREAKING CHANGE: Registry organization responses no longer include _relatedOrganizations. Single-organization responses now expose _hierarchy, and the paginated organization list contains neither field.
Expose each organization's UUID alongside its short name, long name, and children in full and trimmed hierarchy responses. This allows hierarchy nodes to be correlated with reports_to, top_level_root, and oversees references. Update the recursive response schemas and OpenAPI documentation to require UUIDs. Configure hierarchy schema tests with ajv-formats so UUID validation is recognized. Correct populated hierarchy expectations for four child Roots per top-level Root, and update organization-list integration tests to locate records across paginated responses.
Jd heirarchy output
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.
No description provided.