{"action":"created","issue":{"url":"https://api.github.com/repos/ibm-js/delite/issues/366","labels_url":"https://api.github.com/repos/ibm-js/delite/issues/366/labels{/name}","comments_url":"https://api.github.com/repos/ibm-js/delite/issues/366/comments","events_url":"https://api.github.com/repos/ibm-js/delite/issues/366/events","html_url":"https://github.com/ibm-js/delite/issues/366","id":55021861,"number":366,"title":"superCalls on custom setters don't always work on inherited properties","user":{"login":"tkrugg","id":2982512,"avatar_url":"https://avatars.githubusercontent.com/u/2982512?v=3","gravatar_id":"","url":"https://api.github.com/users/tkrugg","html_url":"https://github.com/tkrugg","followers_url":"https://api.github.com/users/tkrugg/followers","following_url":"https://api.github.com/users/tkrugg/following{/other_user}","gists_url":"https://api.github.com/users/tkrugg/gists{/gist_id}","starred_url":"https://api.github.com/users/tkrugg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tkrugg/subscriptions","organizations_url":"https://api.github.com/users/tkrugg/orgs","repos_url":"https://api.github.com/users/tkrugg/repos","events_url":"https://api.github.com/users/tkrugg/events{/privacy}","received_events_url":"https://api.github.com/users/tkrugg/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-01-21T13:59:19Z","updated_at":"2015-01-21T16:39:10Z","closed_at":"2015-01-21T15:07:33Z","body":"If widget Child inherits from Mother a property \"p\", I don't seem to be able to do a superCall on the custom setter of \"p\" inside Child, if such a custom setter didn't exist in Mother.\r\n"},"comment":{"url":"https://api.github.com/repos/ibm-js/delite/issues/comments/70871409","html_url":"https://github.com/ibm-js/delite/issues/366#issuecomment-70871409","issue_url":"https://api.github.com/repos/ibm-js/delite/issues/366","id":70871409,"user":{"login":"AdrianVasiliu","id":1583981,"avatar_url":"https://avatars.githubusercontent.com/u/1583981?v=3","gravatar_id":"","url":"https://api.github.com/users/AdrianVasiliu","html_url":"https://github.com/AdrianVasiliu","followers_url":"https://api.github.com/users/AdrianVasiliu/followers","following_url":"https://api.github.com/users/AdrianVasiliu/following{/other_user}","gists_url":"https://api.github.com/users/AdrianVasiliu/gists{/gist_id}","starred_url":"https://api.github.com/users/AdrianVasiliu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AdrianVasiliu/subscriptions","organizations_url":"https://api.github.com/users/AdrianVasiliu/orgs","repos_url":"https://api.github.com/users/AdrianVasiliu/repos","events_url":"https://api.github.com/users/AdrianVasiliu/events{/privacy}","received_events_url":"https://api.github.com/users/AdrianVasiliu/received_events","type":"User","site_admin":false},"created_at":"2015-01-21T16:39:10Z","updated_at":"2015-01-21T16:39:10Z","body":"I also think we can live with what we have. That said, it may have been nice if the implementation of a custom setter for an inherited property didn't need to be different depending on whether the parent class has a custom setter - the presence of the custom setter on the parent looks as an implementation detail which, in an ideal world, shouldn't impact the way subclasses are coded. Anyway, rather a dcl issue, I agree. My cts."}}