This repository was archived by the owner on Nov 21, 2025. It is now read-only.
Add Abilities API bridge for WP Feature API #90
Closed
Conversation
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
Implements a bridge between WordPress.org Abilities API and WP Feature API, allowing abilities to be automatically registered as features when enabled.
emdashcodes
changed the title
- Change config from useAbilitiesBackend boolean to backend string ('features' | 'abilities')
- Remove unnecessary wp.data availability checks (it's a dependency)
- Fix demo ability registration with proper JSON schema for OpenAI compatibility
- Remove configure() function - config is read once at module load
- Simplify string comparison for wp_localize_script values
emdashcodes
changed the title
Member
|
This is great! Once we publish |
- Add key: 'name' to abilities entity config for core-data - Map ability fields correctly to Feature interface - Fix resolver to handle abilities using name instead of id
Member
|
We are closer to the finish line to make it happen. The last remaining task is to publish a composer package, which is tracked in: |
Member
|
The initial v0.1.0 release for Abilities API is ready. It should get published on Packagist as |
Member
|
https://packagist.org/packages/wordpress/abilities-api – it's ready for testing! |
Collaborator
Author
|
Awesome! I'll retest this against the composer version Monday and get this merged 🎉 |
Member
|
Should we close this one and archive the project on GitHub redirecting folks to use Abilities API v0.2+? |
Collaborator
Author
|
@gziolo Yes good call. I'll archive this repo a bit later today and update the README. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Implements client-side integration between the WordPress Abilities API and the WP Feature API, enabling the Feature API client to use Abilities as the backend for server-side features.
Why
The WordPress Abilities API provides a standardized way to register and manage server capabilities now, and is slated for WordPress core inclusion. This integration allows the Feature API client to leverage abilities as its backend, while still allowing client features to be used (until the Abilities API supports client abilities).
How
When enabled via the
WP_FEATURE_API_ABILITIES_BACKENDconstant or via JS, the Feature API client:/wp/v2/featuresto/wp/v2/abilitiesThe integration is purely client-side - plugins can migrate from
wp_register_feature()towp_register_ability()directly.Testing Steps
define( 'WP_FEATURE_API_ABILITIES_BACKEND', true );in wp-config.phpdefine( 'WP_FEATURE_API_LOAD_DEMO', true );in wp-config.php/wp-admin/options-general.php?page=wp-ai-api-proxy-settingsability/demo/site-infois called