add_portal_admin_api_mutation

To add a Portal Admin GraphQL mutation, first read portal/src/graphql/adminapi/schema.graphql to verify available fields, then create the .graphql file under portal/src/graphql/adminapi/mutations. This schema-first approach prevents inconsistent or ad-hoc mutation definitions.

The correct workflow for adding admin API mutations involves reading the schema.graphql file, creating the new mutation file under the mutations directory querying top-level fields, and running npm run gentype from the portal directory to synchronize generated TypeScript types.

Yes, you must run npm run gentype from the portal directory after adding a new mutation. This type generation handshake updates generated types to reflect the new GraphQL operations, keeping the admin API consistent and type-safe.

You should avoid querying nested entities when creating a portal admin mutation unless explicitly requested. The standard practice is to query only top-level fields from the schema.graphql to maintain consistency and prevent overly complex mutation definitions.

Generated types mismatch after adding a portal admin GraphQL mutation because the type generation handshake was skipped. You must run npm run gentype from the portal directory after creating the mutation file to synchronize the generated types with your new schema operations.

The best way to expand admin operations while maintaining schema fidelity is to review portal/src/graphql/adminapi/schema.graphql before file creation, place the mutation under the mutations directory, and execute npm run gentype to keep generated types synchronized.