Skip to content

GraphQL: document unified revinclude syntax - #41

Merged
aleksandrkislitsyn merged 1 commit into
mainfrom
docs/graphql-unified-revinclude
Aug 26, 2026
Merged

GraphQL: document unified revinclude syntax#41
aleksandrkislitsyn merged 1 commit into
mainfrom
docs/graphql-unified-revinclude

Conversation

@aleksandrkislitsyn

Copy link
Copy Markdown
Contributor

What

Documents the new unified revinclude GraphQL syntax shipped in HealthSamurai/sansara#8232 (part of the GraphQL topics issue HealthSamurai/sansara#8181).

The ### Revincludes section of docs/api/graphql-api.md previously covered only the classic field-per-path style (<sourceType>_as_<path>). This adds a subsection covering:

  • the new setting module.graphql.revinclude-syntax (BOX_MODULE_GRAPHQL_REVINCLUDE_SYNTAX), field-per-path (default) vs. unified
  • the _revinclude(path: "<ResourceType>.<element>") field, with a single-target example and a multi-target (aliased) example
  • the 400 error behavior for an invalid resource type / empty path
  • a hint noting that unified mode does not yet accept search args on the included resources

Verification

All example queries were run against a local Aidbox edge build (commit 35612ac03f, which includes #8232) with BOX_MODULE_GRAPHQL_REVINCLUDE_SYNTAX=unified and confirmed to return the documented results.

Note

The auto-generated settings reference (all-settings) will pick up module.graphql.revinclude-syntax separately once the gen-doc job runs — that is currently blocked by an expired HS_ROBOT_DOCUMENTATION GitHub token and is out of scope for this hand-written page.

🤖 Generated with Claude Code

Document the new module.graphql.revinclude-syntax setting and the
unified `_revinclude(path: ...)` field added in HealthSamurai/sansara#8232
(part of GraphQL topics issue HealthSamurai/sansara#8181).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@aleksandrkislitsyn
aleksandrkislitsyn merged commit a60260f into main Aug 26, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant