Release 2.1.0#30
Merged
Merged
Conversation
Release 2.0.3
add example to FAQ block
Extract shared FAQ schema generation and resolve Yoast or SEOPress at runtime, with both plugins available in wp-env via Composer.
Register a dedicated service using rank_math/json_ld and include the plugin in the local wp-env setup via Composer.
Replace faq__* classes with wp-block-blockparty-faq-* structure, add CSS custom properties, and register deprecated handlers so existing 2.0.x content keeps validating and rendering.
Mirror blockparty-accordion behavior: parent-level control synced to child questions, shown only when accordion mode is enabled.
Clean markup and heading level attribute
Configures Composer to use PSR-4 for the `Blockparty\Faq\` namespace. This involves adding the `autoload` section to `composer.json`, including `vendor/autoload.php`, and renaming class directories (e.g., `schema` to `Schema`) to align with PSR-4 capitalization standards. This improves class management, code organization, and facilitates future development by adhering to modern PHP practices.
SEOPress & Rank Math compat'
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8cf5c45. Configure here.
Refactors heading level synchronization using `useLayoutEffect` and direct calls. This prevents visual delays and inconsistencies when the parent FAQ block's `isAccordion` or `headingLevel` attributes change in the editor.
Ensures that new FAQ questions are merged with existing ones in the schema data, rather than overwriting them. Normalizes the structure of existing questions and renumbers all combined questions to maintain valid Schema.org position values.
Updates the `useSyncQuestionHeadingLevels` hook to leverage `@wordpress/data`'s `useSelect` and `useDispatch` for accessing block editor state and actions. This removes the need to pass the `blockEditor` object as a prop, improving the hook's encapsulation and aligning with modern WordPress block editor development patterns.
Updates the `useSyncQuestionHeadingLevels` hook to explicitly select the inner FAQ question blocks using `useSelect`. By including these blocks in the `useEffect` dependencies, heading levels are now correctly re-synchronized when questions are added, removed, or reordered within the FAQ block.
Fix/bugbot 2.1.0
firestar300
force-pushed
the
release/2.1.0
branch
from
8cf5c45 to
5ebdaf2
Compare
cedric07
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 2.1.0
Note
Medium Risk
Changes affect front-end FAQ markup/CSS selectors and SEO JSON-LD routing across three plugins; incorrect resolver priority or legacy accordion breakage could impact existing sites until content is re-saved.
Overview
Release 2.1.0 bumps the plugin version and documents the release in a new
CHANGELOG.md, with README/readme.txtupdated to match.FAQ JSON-LD no longer assumes Yoast only: PHP is reorganized under PSR-4 (
Schema/,Services/,Hooks/) with aSeo_Service_Resolverthat registers Yoast, Rank Math, or SEOPress via dedicated service classes and sharedFAQ_Schema_Generator. Schema bootstrap moves from legacyincludes/hooks/schema.phptoSchema_Hooks.php.On the block side, the FAQ gains a configurable question heading level (h2–h6) (parent context + inspector), inserter example preview, and front-end markup aligned to WordPress block classes (
.wp-block-blockparty-faq-*); accordion config in PHP now targets those selectors, withscript.jsstill initializing legacy.faq__*markup. Deprecated save handlers preserve 2.0.x stored HTML; the faq-item editor duplicate wrapper fix is part of this release.Local dev shifts SEO plugins to Composer (
wp-packagesrepo →.wp-env/plugins/),.wp-env.jsonmounts all three, npm scripts becomeenv:start/env:stop, and Psalm is removed fromcomposer.json..gitignoreaddscomposer.lockand.wp-env/plugins/.Reviewed by Cursor Bugbot for commit 5ebdaf2. Bugbot is set up for automated code reviews on this repo. Configure here.