v0.3.0

What's Changed

• Proposal: Add ability anotations by @gziolo in #99
• Add new show_in_rest arg to control REST API exposure by @gziolo in #103
• Move show_in_rest to meta in the registration process by @gziolo in #107
• Move new annotations property under meta and update docs by @gziolo in #104
• Introduce invoke_callback helper method in WP_Ability class by @gziolo in #88
• Feature: add categories system by @galatanovidiu in #102
• Create reference docs for client-side API by @jonathanbossenger in #87
• Add category support to client package by @emdashcodes in #114
• Update version to 0.3.0 in preparation to Composer package release by @gziolo in #116
• Update README.md by @karmatosed in #118
• Add category listing endpoints for the REST API by @emdashcodes in #120
• Add category listing and validation to client package by @emdashcodes in #121

Breaking Changes

• It's now mandatory to provide a registered category with wp_register_ability_category() when registering an ability with wp_register_ability().
• It's also mandatory to provide a category name when registering the ability on the client with wp.abilities.registerAbility.
• By default, all abilities are no longer exposed through the REST API. To opt into the old behavior, provide meta containing [ 'show_in_rest' => true ].
• Meta annotations were introduced to control which HTTP method, GET vs POST, is used to execute an ability through the REST API. In particular, if you want to use GET, then make sure to include in meta the following override [ 'annotations' => [ 'readonly' => true ] ].

New Contributors

• @galatanovidiu made their first contribution in #102
• @karmatosed made their first contribution in #118

Full Changelog: v0.2.0...v0.3.0-rc.2