pat-contentbrowser: unused and missing pattern arguments

[thet]

While trying to customize the SelectedItem component of the contentbrowser app, I recognized the following:

• The selection-template argument is nowhere used. It can probably removed.
• The layout Svelte property is not defined in the parser, but documented and used in the code. It cannot be configured via pattern options and need to be added to the arguments.
• The custom-component-keys argument is documented, but in code it is used as componentRegistryKeys. This maybe should be aligned to the documentation, as I think the naming of custom-component-keys is more clear than component-registry-keys. Is is it already used in production and therefore the documentation should be adapted? We can also add an alias, so there is a BBB compatibility with old code.

[petschki]

• The selection-template argument is nowhere used. It can probably removed.

This was introduced in the beginning to provide the same options as pat-relateditems has. Though it never was implemented. We should refer here to the customizable custom components.

• The layout Svelte property is not defined in the parser, but documented and used in the code. It cannot be configured via pattern options and need to be added to the arguments.

+1

• The custom-component-keys argument is documented, but in code it is used as componentRegistryKeys. This maybe should be aligned to the documentation, as I think the naming of custom-component-keys is more clear than component-registry-keys. Is is it already used in production and therefore the documentation should be adapted? We can also add an alias, so there is a BBB compatibility with old code.

+1 on all. Its currently in use by an addon of us so an alias would be nice.