Thank you for going back to make this API stable. I support the idea!

Do you know why useResourcePermission is used only in one place? Isn't it something that would also be useful to integrate with the Reusable block or the Template Part block?

I would expect to see the JSDoc for the stable now function included in the README file of the @wordpress/core-data package. As part of the documentation process, we should also include it in the CHANGELOG file of the package.

As for the dev note, it's something that should be compiled together with other changes to the package – new API for useEntityRecord and useEntityRecords.

@gziolo I just added the README and Changelog entries, good call!

Do you know why useResourcePermission is used only in one place? Isn't it something that would also be useful to integrate with the Reusable block or the Template Part block?

Good call as well, I can see other places where this would be useful. Let's pursue the refactor separately from this PR.

Size Change: +657 B (0%)

Total Size: 1.24 MB

_{compressed-size-action}

Here's the PR where I explore the refactor: #43305

We have now a few more places to update __experimentalUseResourcePermissions and we are done 🎉

In other news, this is the last task that concludes the proposal from https://make.wordpress.org/core/2022/07/04/proposal-better-rest-api-handling-in-javascript/. The only task left is compiling a dev note covering all final changes and enriching the documentation with the new APIs after WordPress 6.1 is out. Everything here is built on top of existing public APIs, so that means we eventually need to decrease the visibility of low-level APIs in the Block Editor Handbook.

Awesome work @adamziel 🚀

Thanks, @adamziel. I agree that the hook was ready for stabilization.

The one issue I would like to see resolved, and it's not entirely related to this hook, is the one I mentioned in #35527 (comment).

When using this hook, even if you only check for single permission, it will still make multiple calls to the same endpoint.

While a few extra API calls aren't necessarily bad, numbers will add up as we continue adoption in the core.

Example

var el = wp.element.createElement;
var __ = wp.i18n.__;
var registerPlugin = wp.plugins.registerPlugin;
var PluginDocumentSettingPanel = wp.editPost.PluginDocumentSettingPanel;
var useResourcePermissions = wp.coreData.useResourcePermissions;
 
function MyDocumentSettingPlugin() {
    // Replace tag ID.
    const { canUpdate } = useResourcePermissions( 'tags', 20 );

    if ( ! canUpdate ) {
        return null;
    }

    return el(
        PluginDocumentSettingPanel,
        {
            className: 'my-document-setting-plugin',
            title: 'Permissions',
        },
        __( 'User has required Permissions' )
    );
}
 
registerPlugin( 'my-document-setting-plugin', {
    render: MyDocumentSettingPlugin,
} );

@Mamaduka good note! As you noticed, it is not specific to this hook - see this patch for canUser resolver I just prepared.

Dev note proposed at https://make.wordpress.org/core/?p=99829&preview=1&_ppp=2b1db975ea