Currently, the GraphQL Compose Webform module does not expose form element validation properties such as required, required_error, pattern, pattern_error, and other validation-related options via the GraphQL schema. This is a limitation when building decoupled or headless applications that rely on Webform data to dynamically generate and validate frontend forms.
Developers are unable to retrieve essential validation rules that are configured in the Webform UI, making it difficult to replicate Drupal-side validation logic on the client-side using GraphQL.
Extend the GraphQL Compose Webform module to include validation-related properties for each element in the GraphQL schema and output. This could be done by:
validation object to each webform element type, including:
required (boolean)required_error (string)counter (boolean)counter_type (string)pattern (string)pattern_error (string)minlength, maxlength (integer)Ensure this metadata is included in both the schema definition and the actual query response. This enhancement will allow frontend frameworks to implement the same validation logic as Drupal's Webform.
None expected in the Drupal admin UI. This change only affects the GraphQL schema and API consumers.
GraphQL schema will be extended to expose additional validation metadata for webform elements.
No changes to the underlying Drupal data model or storage. This is purely an enhancement to GraphQL output.
Active
1.3
Code
This patch addresses the issue by extending the GraphQL schema for Webform elements to include key validation properties.
I have updated the GraphQL Compose Webform patch to include support for the Advanced HTML/Text field. The text data from this field is now correctly appearing in the GraphQL output.
webform {
id
elements {
text
}