inteligr8/alfresco-ng2-components
1
0
Fork 0
mirror of https://github.com/Alfresco/alfresco-ng2-components.git synced 2025-07-24 17:32:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

[ADF-4285] Removed incorrect example from content metadata docs (#4564)

Browse Source
This commit is contained in:
Andy Stark
2019-04-05 17:24:06 +01:00
committed by Eugenio Romano
parent d817f3aaa3
commit 4339af9f42
1 changed files with 2 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/content-services/components/content-metadata-card.component.md
View File

@@ -255,9 +255,9 @@ Futhermore, you can also exclude specific aspects by adding the `exclude` proper
}, },
``` ```
When using this configuration you can still whitelist aspects and properties as you desire. Let's see more complex examples for each of the config layouts: When using this configuration you can still whitelist aspects and properties as you desire. The
example below shows this with an aspect-oriented config:
##### Aspect oriented config
```json ```json
"content-metadata": { "content-metadata": {
"presets": { "presets": {
@@ -270,26 +270,6 @@ When using this configuration you can still whitelist aspects and properties as
}, },
``` ```
##### Layout oriented config
```json
"content-metadata": {
"presets": {
"robot-images": [
{
"includeAll": true,
"exclude": ["cm:content", "exif:exif"]
},
{
"title": "Robot Group",
"items": [
{ "aspect": "exif:exif", "properties": [ "exif:pixelXDimension", "exif:pixelYDimension"] }
]
}
]
}
},
```
## What happens when there is a whitelisted aspect in the config but the given node doesn't relate to that aspect ## What happens when there is a whitelisted aspect in the config but the given node doesn't relate to that aspect
Nothing - since this aspect is not related to the node, it will simply be ignored and not Nothing - since this aspect is not related to the node, it will simply be ignored and not