1.1.0
Paragraph bundles are now first-class scaffold targets, closing the gap where gqcc:inspect and gqcc:generate covered node bundles only.
Added
- gqcc:inspect lists paragraph bundles enabled in graphql_compose (entity_config enabled + query_load_enabled, per-field field_config enablement; both the 2.x config name and 3.x per-server names), with a nested-only marker for bundles that render inside their parents. (#3613218)
- Four paragraph artefacts mirroring the node set: paragraphs/types.generated.d.ts (types joining the DrupalParagraph union), paragraphs/fragments.generated.ts (the PARAGRAPH_FRAGMENTS block), paragraphs/paragraph-renderer-cases.generated.tsx, and one {Name}Paragraph component stub per bundle.
- Response-key collision handling: when two bundles select the same field name with incompatible shapes (required vs optional sub-fields), the later bundle's field is aliased (tabItems: items) and the TypeScript property follows the alias; aliases are stable across --bundles subset runs.
- Nested paragraph references emit nested inline fragments for handler_settings.target_bundles, one level deep, with bundle-specific TypeScript types.
- WebformMapper: webform fields map to a DrupalWebform type with the full graphql_compose_webform selection instead of unknown. (#3613232)
Changed
- --bundles now filters paragraph bundles for generate, diff, validate, and inspect; a paragraph-only run no longer aborts or overwrites node artefacts.
- Paragraph component stubs use the data prop and {Name}Paragraph naming.
- Generated fields are emitted in machine-name order for deterministic output.
- Schema-change log notices emit a working command for paragraph bundles and name the matching renderer on bundle deletion.
Fixed
- PathGuard rejects the macOS /private variants of dangerous filesystem roots. (#3613237)
Full details in CHANGELOG.md. Test suite: 45 tests across Drupal 10.6, 11.3, and 11.