…items

…user_`.

…p-graphql into check-if-nodes-are-resolved

feat: check if nodes are resolved

fix: `UsersConnectionSearchColumnEnum` values should be prefixed with `user_`

fix: return empty when filtering `menuItems` by a `location` with no assigned items

feat: add `UniformResourceIdentifiable` interface to `Comment` type

…_item_connected_node

feat: add `graphql_pre_resolve_menu_item_connected_node` filter

…returns a `ContentType` that `isPostsPage` field returns true

…ble Interface as any node with a URI should be able to identify whether it is or is not the posts page or front page. Defaults to false, but individual implementing types (ContentType, Page) can override the resolver as applicable.

- update the PostType Model to return true if show_on_front is set to "page" and update Post model to return `false` for `isPostsPage` as a Post Object won't ever resolve as the posts page based on the current NodeResolver strategy (see: https://github.com/wp-graphql/wp-graphql/blob/develop/src/Data/NodeResolver.php#L226)

…tent-type

fix: isPostsPage on content type

…argument don't throw errors. It's supposed to pass a string, but it's been reported to not always pass a string.

… output any other errors

…ssible' into develop

revert back to old workflow

…_enqueu_scripts-callback

fix: admin_enqueue_scripts callback should expect a possible null value passed to it

- update inconsistent @todo tag

…v1.22.0

…elease

ci: pin wp-browser to "<3.5" to allow automated tests to run properly

Co-authored-by: Dovid Levine <[email protected]>

Co-authored-by: Dovid Levine <[email protected]>

- update tested up to in main plugin and readme