GraphQL Support for dotAssets and FileAssets in Image/File Fields

Description

Currently, when querying content with asset relationships through GraphQL, there are critical issues affecting both dotAssets and FileAssets:

1. User created fields not accessible - User created fields on dotAssets and FileAssets cannot be queried through GraphQL, blocking AI tagging workflows and rich metadata access.

2. Incomplete GraphQL schema - The DotAsset type definition is missing 20+ properties that are available via _map, including: fileName, publishDate, mimeType, size, extension, url, creationDate, name, shortyId, and others. This breaks GraphQL's self-documenting nature and forces developers to rely on the _map escape hatch.

• The GraphQL schema for DotAsset exposes all available properties through schema introspection
• Custom fields defined on dotAsset and FileAsset content types are queryable via GraphQL
• Developers can build headless applications without N+1 query patterns or _map workarounds

Target Personas

• Developer teams

Links

• Full Context