- clean up switch statement, removing any cases that are not explicitly triggered. That will allow the wpgraphql/acf/match_location_rule action to fire and the other rules can be compensated via that action

Author: jasonbahl

src/LocationRules/LocationRules.php

@@ -266,12 +266,6 @@ public function determine_rules( string $field_group_name, string $param, string
 			case 'page_template':
 				$this->determine_post_template_rules( $field_group_name, $param, $operator, $value );
 				break;
-			case 'post_status':
-				break;
-			case 'post_format':
-			case 'post_category':
-			case 'post_taxonomy':
-				break;
 			case 'post':
 				$this->determine_post_rules( $field_group_name, $param, $operator, $value );
 				break;
@@ -284,15 +278,6 @@ public function determine_rules( string $field_group_name, string $param, string
 				// we can add the field group to the Page type
 				$this->set_graphql_type( $field_group_name, 'Page' );
 				break;
-			case 'current_user':
-			case 'current_user_role':
-				// @todo:
-				// Right now, if you set current_user or current_user_role as the only rule,
-				// ACF adds the field group to every possible location in the Admin.
-				// This seems a bit heavy handed. 🤔
-				// We need to think through this a bit more, and how this rule
-				// Can be composed with other rules, etc.
-				break;
 			case 'user_form':
 			case 'user_role':
 				// If user_role or user_form params are set, we need to expose the field group
@@ -308,9 +293,6 @@ public function determine_rules( string $field_group_name, string $param, string
 			case 'comment':
 				$this->determine_comment_rules( $field_group_name, $param, $operator, $value );
 				break;
-			case 'widget':
-				// @todo: Widgets are not currently supported in WPGraphQL
-				break;
 			case 'block':
 				$this->determine_block_rules( $field_group_name, $param, $operator, $value );
 				break;