create-api-journeys-override

Creates Federation @override entries migrating fields between api-journeys GraphQL schemas.

25|15|Updated Aug 2, 2021
One-click install
npx skills add https://github.com/JesusFilm/core --skill create-api-journeys-override
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-api-journeys-override
Source: https://github.com/JesusFilm/core/tree/main/.cursor/skills/create-api-journeys-override
Command: npx skills add https://github.com/JesusFilm/core --skill create-api-journeys-override

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate and align GraphQL field resolution between legacy api-journeys and modern api-journeys-modern by enabling precise overrides with Federation @override.

Core Features & Use Cases

  • Create override files for specific fields (queries, mutations, or resolvers) to migrate behavior without rewriting all downstream logic.
  • Validate SDL match (return types, args) and apply overrides with correct federation semantics.
  • Regenerate the GraphQL schema and tests to reflect the migrated field, keeping schema compatibility.

Quick Start

Create the override for a target field, implement necessary Pothos types if missing, and regenerate the schema.

Frequently Asked Questions about create-api-journeys-override

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I override GraphQL fields when migrating to a new federated subgraph?

To override GraphQL fields during a federated schema migration, apply the Federation @override directive to specific queries, mutations, or resolvers to shift resolution from a legacy subgraph to a modern one without rewriting downstream logic.

What is the best way to migrate queries from NestJS to Pothos in a GraphQL Federation?

Migrating queries from NestJS to Pothos in a GraphQL Federation requires creating override files for target fields, ensuring SDL-aligned return types and arguments, and regenerating the schema to reflect the migrated behavior accurately.

Do I need to match SDL return types when applying GraphQL Federation overrides?

Yes, applying GraphQL Federation overrides requires SDL-aligned return types and arguments between legacy and modern schemas to maintain schema compatibility and ensure correct federation semantics during field resolution.

How do I regenerate a GraphQL schema after moving field resolvers to a modern implementation?

After moving field resolvers to a modern implementation, regenerate the GraphQL schema and execute tests to verify that the new Pothos types and @override directives reflect the migrated field behavior correctly.

Can I migrate individual GraphQL mutations without rewriting the entire schema?

Yes, you can migrate individual GraphQL mutations by creating specific override files for target fields, allowing you to shift behavior from a legacy api-journeys schema to a modern one without rewriting all downstream logic.