Text Processingflags: g

GraphQL Operation Header

Match GraphQL operation headers — `query`, `mutation`, or `subscription` — capturing the operation name.

Try it in RegexPro →

Available in

JSSupported

JavaScript / ECMAScript

Browser-native RegExp. Default if you don't pick.

PYSupported

Python (re)

CPython stdlib `re`. Unicode-aware `\w` and `\d` by default.

GOSupported

Go (RE2)

Linear-time matching. No backreferences or lookarounds.

Pattern

regexengine-agnostic
(query|mutation|subscription)\s+(\w+)?\s*(?:\([^)]*\))?\s*\{   (flags: g)

Raw source: (query|mutation|subscription)\s+(\w+)?\s*(?:\([^)]*\))?\s*\{

How it works

(query|mutation|subscription) captures the operation type. \s+(\w+)? optionally captures the operation name (anonymous operations omit it). (?:\([^)]*\))? optionally matches a variables declaration `($var: Type)`. The trailing `\s*\{` matches the opening brace of the selection set.

Examples

Input

query GetUser($id: ID!) { user(id: $id) { name } }

Matches

  • query GetUser($id: ID!) {

Input

mutation { createPost(title: "hi") { id } }

Matches

  • mutation {

Input

// not graphql

No match

—

Common use cases

  • •GraphQL operation registry / persisted-queries
  • •Linting (require named operations, etc.)
  • •Apollo / urql client introspection
  • •Static analysis for n+1 query risks
←PreviousXML Namespace Declaration
All patterns
NextOpenAPI Path Template→