new-external-api-object

To add a new external API object across multiple surfaces, use API-independent descriptors with proper inheritance and interface wiring. This pattern ensures consistent exposure via GraphQL, REST, and gRPC while applying backward-compat rules to avoid breaking existing clients.

The descriptor-based approach defines API-independent models that support inheritance and interfaces. These descriptors are then wired consistently into GraphQL, REST, and gRPC surfaces using specific converters, ensuring type-safe polymorphic exposure across at least two APIs.

You implement per-parameter caches and builder patterns by following the descriptor-based workflow provided for new API objects. This approach ensures scalable and type-safe API surface generation across multiple external API endpoints.

You need descriptor inheritance when introducing a suffix variant or a brand-new object that must be exposed via at least two of the three external APIs. Inheritance ensures the variant integrates correctly with interface wiring and per-API converters.

Yes, the pattern provides specific GraphQL and gRPC converters. These converters translate the API-independent descriptors into the respective API formats while enforcing backward-compatibility rules to maintain stable client interactions.

The primary constraint is maintaining backward compatibility. The new object, suffix variant, or polymorphic interface must be exposed via at least two APIs using the provided descriptor patterns to avoid breaking existing clients.