chore: relocate AbstractConnectionResolver::is_valid_offset() with other abstract methods

justlevine · justlevine · commit e10139e7de40 · 2024-05-04T01:49:21.000Z
diff --git a/src/Data/Connection/AbstractConnectionResolver.php b/src/Data/Connection/AbstractConnectionResolver.php
@@ -260,6 +260,17 @@ abstract public function get_query_args();
 	 */
 	abstract public function get_query();
 
+	/**
+	 * Determine whether or not the the offset is valid, i.e the item corresponding to the offset exists.
+	 *
+	 * Offset is equivalent to WordPress ID (e.g post_id, term_id). So this is equivalent to checking if the WordPress object exists for the given ID.
+	 *
+	 * @param mixed $offset The offset to validate. Typically a WordPress Database ID
+	 *
+	 * @return bool
+	 */
+	abstract public function is_valid_offset( $offset );
+
 	/**
 	 * Used to determine whether the connection query should be executed. This is useful for short-circuiting the connection resolver before executing the query.
 	 *
@@ -294,19 +305,6 @@ protected function max_query_amount(): int {
 		return 100;
 	}
 
-	/**
-	 * Is_valid_offset
-	 *
-	 * Determine whether or not the the offset is valid, i.e the item corresponding to the offset
-	 * exists. Offset is equivalent to WordPress ID (e.g post_id, term_id). So this function is
-	 * equivalent to checking if the WordPress object exists for the given ID.
-	 *
-	 * @param mixed $offset The offset to validate. Typically a WordPress Database ID
-	 *
-	 * @return bool
-	 */
-	abstract public function is_valid_offset( $offset );
-
 	/**
 	 * Return an array of ids from the query
 	 *
