Fix operation_name not being set in juniper_hyper (#1169, #1187)

graphql-rust · Sep 12, 2023 · f172be5 · f172be5
1 parent dadd318
commit f172be5
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/juniper_actix/CHANGELOG.md b/juniper_actix/CHANGELOG.md
@@ -14,7 +14,13 @@ All user visible changes to `juniper_actix` crate will be documented in this fil
 - Switched to 0.16 version of [`juniper` crate].
 - Switched to 0.4 version of [`juniper_graphql_ws` crate].
 
+### Fixed
+
+- `operationName` not being set. ([#1187], [#1169])
+
 [#1034]: /../../pull/1034
+[#1169]: /../../issues/1169
+[#1187]: /../../pull/1187
 
 
 

diff --git a/juniper_hyper/src/lib.rs b/juniper_hyper/src/lib.rs
@@ -212,7 +212,7 @@ where
     S: ScalarValue,
 {
     let mut query = None;
-    let operation_name = None;
+    let mut operation_name = None;
     let mut variables = None;
     for (key, value) in form_urlencoded::parse(input.as_bytes()).into_owned() {
         match key.as_ref() {
@@ -226,6 +226,7 @@ where
                 if operation_name.is_some() {
                     return Err(invalid_err("operationName"));
                 }
+                operation_name = Some(value)
             }
             "variables" => {
                 if variables.is_some() {