Skip to content

feat: return error if federated graph has no query root type#12

Merged
Aenimus merged 1 commit intodavid/eng-3753-add-argument-configurationfrom
david/eng-3808-return-error-if-no-query-root-type
Aug 25, 2023
Merged

feat: return error if federated graph has no query root type#12
Aenimus merged 1 commit intodavid/eng-3753-add-argument-configurationfrom
david/eng-3808-return-error-if-no-query-root-type

Conversation

@Aenimus
Copy link
Copy Markdown
Member

@Aenimus Aenimus commented Aug 25, 2023

Motivation and Context

@linear
Copy link
Copy Markdown

linear Bot commented Aug 25, 2023

@Aenimus Aenimus merged commit 4d831cc into david/eng-3753-add-argument-configuration Aug 25, 2023
@ysmolski ysmolski deleted the david/eng-3808-return-error-if-no-query-root-type branch September 1, 2025 14:24
jensneuse added a commit that referenced this pull request Apr 24, 2026
…review #7, #12)

- #7: rename benchmark mode cache_disabled -> entity_cache_disabled so
  the label reflects what is actually disabled (X-WG-Disable-Entity-Cache
  only; there is no router header for query-cache). Updated in lib.ts,
  lib.test.ts, and scenarios/cache-demo.json.
- #12: document cross-subgraph TTL divergence in docs/entity-caching/directives.md.
  The composed router config keeps per-datasource entityCacheConfigurations
  entries (demo/cachegraph Article maxAge: 120, demo/cachegraph-ext Article
  maxAge: 90 are preserved separately). Coderabbit's claim that composition
  collapses them was incorrect; the section now explicitly states the real
  behavior and recommends aligning maxAge values for shared entity types.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant