{"action":"opened","issue":{"url":"https://api.github.com/repos/Alfresco/alfresco-ng2-components/issues/4992","repository_url":"https://api.github.com/repos/Alfresco/alfresco-ng2-components","labels_url":"https://api.github.com/repos/Alfresco/alfresco-ng2-components/issues/4992/labels{/name}","comments_url":"https://api.github.com/repos/Alfresco/alfresco-ng2-components/issues/4992/comments","events_url":"https://api.github.com/repos/Alfresco/alfresco-ng2-components/issues/4992/events","html_url":"https://github.com/Alfresco/alfresco-ng2-components/issues/4992","id":480693226,"node_id":"MDU6SXNzdWU0ODA2OTMyMjY=","number":4992,"title":"adf-content-metadata-card configuration driven by node-type doesn't work for cm:content","user":{"login":"shazada","id":1477763,"node_id":"MDQ6VXNlcjE0Nzc3NjM=","avatar_url":"https://avatars2.githubusercontent.com/u/1477763?v=4","gravatar_id":"","url":"https://api.github.com/users/shazada","html_url":"https://github.com/shazada","followers_url":"https://api.github.com/users/shazada/followers","following_url":"https://api.github.com/users/shazada/following{/other_user}","gists_url":"https://api.github.com/users/shazada/gists{/gist_id}","starred_url":"https://api.github.com/users/shazada/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/shazada/subscriptions","organizations_url":"https://api.github.com/users/shazada/orgs","repos_url":"https://api.github.com/users/shazada/repos","events_url":"https://api.github.com/users/shazada/events{/privacy}","received_events_url":"https://api.github.com/users/shazada/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-08-14T13:54:31Z","updated_at":"2019-08-14T13:54:31Z","closed_at":null,"author_association":"NONE","body":"<!--\r\nPLEASE FILL OUT THE FOLLOWING INFORMATION, THIS WILL HELP US TO RESOLVE YOUR PROBLEM FASTER.\r\n\r\nREMEMBER FOR SUPPORT REQUESTS YOU CAN ALSO ASK ON OUR GITTER CHAT:\r\nPlease ask before on our gitter channel https://gitter.im/Alfresco/alfresco-ng2-components\r\n-->\r\n\r\n**Type of issue:**  (check with \"[x]\")\r\n\r\n> - [ ] New feature request\r\n> - [x] Bug  \r\n> - [ ] Support request\r\n> - [ ] Documentation\r\n\r\n**Current behaviour:**\r\nAt the moment the only way to display the 'default' properties like name size etc.\r\nis by enabling the toggle in the HTML component with [displayDefaultProperties]=\"true\">\r\nThe problem is, this creates an additional preset which get's shown per default. When clicking on less information the custom preset is shown and then your custom properties are visible.\r\n\r\nAccording to issue #2893 and the documentation it's possible to configure it like this:\r\nhttps://www.alfresco.com/abn/adf/docs/content-services/components/content-metadata-card.component/#basic-elements\r\n\r\n`\"content-metadata\": {\r\n        \"presets\": {\r\n          \"file_preset\": [{\r\n            \"title\": \"File details\",\r\n            \"items\": [\r\n                { \"aspect\": \"cm:titled\", \"properties\": \"*\"},\r\n                { \"type\": \"cm:content\", \"properties\": [\"cm:name\"]}\r\n            ]}],\r\n      ]}\r\n    }`\r\n\r\nBut if [displayDefaultProperties]=\"false\" cm:content will be called and visible on edit-mode but will have no value.\r\n\r\n**Expected behavior:**\r\nExpected to add the default properties within a preset configuration\r\n\r\n**Steps to reproduce the issue:**\r\nJust follow the documentation to create a custom preset.\r\nSet the [displayDefaultProperties]=\"false\" and define the above preset.\r\n\r\n**Component name and version:** \r\nadf-content-metadata-card 3.0.0\r\n\r\n**Browser and version:** \r\n<!-- [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ] -->\r\nFirefox Quantum\r\n \r\n**Node version (for build issues):**  \r\n<!-- To check the version: node --version -->\r\n\r\n**New feature request:**\r\n<!-- Describe the feature, motivation and the concrete use case (only in case of new feature request) -->\r\n"}}
{"actor":{"display_login":"shazada"}}