Fill gaps from assistant conversations: nested hierarchy modeling#292
Open
mintlify[bot] wants to merge 2 commits into
Open
Fill gaps from assistant conversations: nested hierarchy modeling#292mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Clarify how to model nested product hierarchies with Velt when Locations are flat, and how to roll up activity across a hierarchy.
Changes
key-concepts/overview.mdx— Explicitly state Locations are flat (cannot be nested), and add a "Modeling nested hierarchies" subsection explaining how to combine Folders/subfolders, Documents, Locations with custom hierarchy fields, and cross-document activity rollups.async-collaboration/activity/overview.mdx— Document the cross-document rollup pattern (passing multipledocumentIds) and note that filtering by custom metadata must happen client-side after subscribing.Context
Recent assistant conversations showed repeated confusion around whether Locations can be nested, how to represent multi-level entity trees (e.g. Style → Variant → SKU), and how to query or roll up activity across such a hierarchy. The APIs already support these patterns; the docs did not spell out the recommended shape.