Provide the client with `create` operation access information similar to #3516657

Should this be postponed on #3498525: [META] Allow Canvas to be used on any content entity type (bundle), as long as it has certain entity type characteristics

#4++

This is a beta blocker because without this, the following will always be visible:

Secondarily, this hard-blocked #3513566: [later phase] [PP-1] Add generic create entity support (currently just `Page` content entities).

Adjusted the proposal.

Note that this can assume a single XB field per content entity type+bundle, if that changes in #3526189: Spike: explore merits of one Canvas field per exposed slot in content templates, it'll be up to that issue to tweak the logic introduced here.

Looks great!

One question, plus needs a follow-up for fixing cacheability.

Already approved 👍

I wanted to merge this, but on a final pass I'm afraid that the proposal was too incomplete after my adjustment in #6. 😅

The MR lets the XB UI know which content entities can be created, and what the label for that should be. But … it doesn't let you know where that is! 😅

So: this should AFAICT:

1. use \Drupal\experience_builder\Resource\XbResourceLinkCollection
2. point to experience_builder.api.content.create

(So: much like \Drupal\experience_builder\Controller\ApiContentControllers::getEntityOperations().)

This would then also immediately give us a nice way to pass the cacheability to make #3531858: CanvasController's response must vary by access result cacheability tighter scoped; otherwise that would have to go and modify the method this had just added.

Nope, that's because XB controls the "create entity" route: experience_builder.api.content.create — which is why simple booleans suffice, and the XB UI can then call its contentApi.createContent.

Attaching the patch that I had written locally, but which fails on the way it tries to pass the label via XbResourceLink's target attributes, because it's a translatable string, not a plain string.

Merged :)

This unblocked #3513566: [later phase] [PP-1] Add generic create entity support (currently just `Page` content entities), and increased the need for #3531858: CanvasController's response must vary by access result cacheability.

I'm slightly too late to the party but I've just merged in upstream changes over at #3516641: Make the XB UI show only UI elements/operations available to the current user and the shape of the permissions object is now more complex as a result of this and as a result is going to make the FE code more complex to work around it.

Previously xb.permissions was a simple

interface permissions {
  [key: string]: boolean;
}

This made it easy for the FE to quickly assert if a user had or did not have a given permission by simply checking that list of booleans.

Can this new contentEntityCreateOperations object be moved into the root of drupalSettings.xb instead of inside the permissions object?

#15: or … what about going from this which was merged:

"permissions": {
  …
  "contentTemplates": false,
  "contentEntityCreateOperations":{
    "xb_page":{"xb_page":"Page"},
     "node":{"article":"Amazing article"}
   }
}

to

"permissions": {
  …
  "contentTemplates": false,
  "create:xb_page": 'Page",
  "create:node:article": "Amazing article",
}

?

(Casting that string to a boolean is trivial.)

I think the format of contentEntityCreateOperations which was merged is more useful because it's easy to iterate over to build the list of "New x" buttons in the UI. Your proposal in #16 means, to build the list of "New x" buttons, I would have to iterate over the permissions object, filter to just keys that starts with 'create:' and then split the key by : to get the entity type and bundle info.

Maybe there is some value to having the permissions listed in the permissions object as you propose, but I think only if that was in addition to still having the info in the original format elsewhere e.g. drupalSettings.xb.contentEntityCreateOperations

"contentEntityCreateOperations":{
    "xb_page":{"xb_page":"Page"},
     "node":{"article":"Amazing article"}
   }