{"action":"created","issue":{"url":"https://api.github.com/repos/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/325","repository_url":"https://api.github.com/repos/aurelia-ui-toolkits/aurelia-kendoui-bridge","labels_url":"https://api.github.com/repos/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/325/labels{/name}","comments_url":"https://api.github.com/repos/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/325/comments","events_url":"https://api.github.com/repos/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/325/events","html_url":"https://github.com/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/325","id":131048487,"number":325,"title":"normalize template custom elements","user":{"login":"JeroenVinke","id":2189477,"avatar_url":"https://avatars.githubusercontent.com/u/2189477?v=3","gravatar_id":"","url":"https://api.github.com/users/JeroenVinke","html_url":"https://github.com/JeroenVinke","followers_url":"https://api.github.com/users/JeroenVinke/followers","following_url":"https://api.github.com/users/JeroenVinke/following{/other_user}","gists_url":"https://api.github.com/users/JeroenVinke/gists{/gist_id}","starred_url":"https://api.github.com/users/JeroenVinke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JeroenVinke/subscriptions","organizations_url":"https://api.github.com/users/JeroenVinke/orgs","repos_url":"https://api.github.com/users/JeroenVinke/repos","events_url":"https://api.github.com/users/JeroenVinke/events{/privacy}","received_events_url":"https://api.github.com/users/JeroenVinke/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-03T14:53:33Z","updated_at":"2016-02-03T15:38:14Z","closed_at":null,"body":"Idea of @charlespockert was to reuse some template custom elements.\r\n\r\nFor example, the listview has a customizable template:\r\n\r\n```\r\n    <k-list-view k-data-source.bind=\"dataSource\">\r\n      <k-list-template>\r\n        ${var}\r\n      </k-list-template>\r\n   </k-list-view>\r\n```\r\n\r\nThe scheduler has one too:\r\n\r\n```\r\n    <k-scheduler>\r\n      <k-event-template>\r\n        ${var}\r\n      </k-event-template>\r\n   </k-scheduler>\r\n```\r\n\r\nThe code of `k-event-template` and `k-list-template` is almost identical. For consistency and code reusability we should look into using a common custom element."},"comment":{"url":"https://api.github.com/repos/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/comments/179297813","html_url":"https://github.com/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/325#issuecomment-179297813","issue_url":"https://api.github.com/repos/aurelia-ui-toolkits/aurelia-kendoui-bridge/issues/325","id":179297813,"user":{"login":"charlespockert","id":9073518,"avatar_url":"https://avatars.githubusercontent.com/u/9073518?v=3","gravatar_id":"","url":"https://api.github.com/users/charlespockert","html_url":"https://github.com/charlespockert","followers_url":"https://api.github.com/users/charlespockert/followers","following_url":"https://api.github.com/users/charlespockert/following{/other_user}","gists_url":"https://api.github.com/users/charlespockert/gists{/gist_id}","starred_url":"https://api.github.com/users/charlespockert/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/charlespockert/subscriptions","organizations_url":"https://api.github.com/users/charlespockert/orgs","repos_url":"https://api.github.com/users/charlespockert/repos","events_url":"https://api.github.com/users/charlespockert/events{/privacy}","received_events_url":"https://api.github.com/users/charlespockert/received_events","type":"User","site_admin":false},"created_at":"2016-02-03T15:38:14Z","updated_at":"2016-02-03T15:38:14Z","body":"@adriatic I'd say sooner is better though as this affects the API\r\n\r\n@JeroenVinke I'm wondering if we can do something where we use a single custom element but maybe use dynamic properties (not sure what's possible as I've not looked at them yet). This way you'd always use `k-template` for example and it would be a single convention to follow throughout.\r\n\r\nOn quick glance it looks like all templates have the same pattern (grab the HTML content in the `@processContent` decorator) so they all share the same basic functionality.\r\n\r\nIf we took this approach, in the case that we find we need special functionality for a certain template type, we could just use composition again - we could add an edge case and make the `k-template` element aware of the parent element type and then handle accordingly"}}