{"action":"created","issue":{"url":"https://api.github.com/repos/dart-lang/reflectable/issues/52","labels_url":"https://api.github.com/repos/dart-lang/reflectable/issues/52/labels{/name}","comments_url":"https://api.github.com/repos/dart-lang/reflectable/issues/52/comments","events_url":"https://api.github.com/repos/dart-lang/reflectable/issues/52/events","html_url":"https://github.com/dart-lang/reflectable/issues/52","id":120592886,"number":52,"title":"Allow access to both getter and setter of a property when either is annotated according to InstanceInvokeMetaCapability ","user":{"login":"lassedamgaard","id":6475621,"avatar_url":"https://avatars.githubusercontent.com/u/6475621?v=3","gravatar_id":"","url":"https://api.github.com/users/lassedamgaard","html_url":"https://github.com/lassedamgaard","followers_url":"https://api.github.com/users/lassedamgaard/followers","following_url":"https://api.github.com/users/lassedamgaard/following{/other_user}","gists_url":"https://api.github.com/users/lassedamgaard/gists{/gist_id}","starred_url":"https://api.github.com/users/lassedamgaard/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lassedamgaard/subscriptions","organizations_url":"https://api.github.com/users/lassedamgaard/orgs","repos_url":"https://api.github.com/users/lassedamgaard/repos","events_url":"https://api.github.com/users/lassedamgaard/events{/privacy}","received_events_url":"https://api.github.com/users/lassedamgaard/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-12-05T22:36:16Z","updated_at":"2015-12-07T07:48:09Z","closed_at":"2015-12-07T07:48:09Z","body":"It would be very nice if you could use InstanceInvokeMetaCapability to reflect on properties without requiring that both getter and setter be annotated with the specified type, either as the default behavior of through additional config. It's less ideal that users of my library have to annotate both getter and setter of every property that they want to have processed when the thing it does always involves both reading and modifying the property value. Currently I have to resort to InstanceInvokeCapability without a name pattern. \r\n\r\nOn a more general note, as a user of Reflectable it would just feel more natural if properties were given at least partially first-class treatment instead of them just being linked by name. "},"comment":{"url":"https://api.github.com/repos/dart-lang/reflectable/issues/comments/162439467","html_url":"https://github.com/dart-lang/reflectable/issues/52#issuecomment-162439467","issue_url":"https://api.github.com/repos/dart-lang/reflectable/issues/52","id":162439467,"user":{"login":"sigurdm","id":8613953,"avatar_url":"https://avatars.githubusercontent.com/u/8613953?v=3","gravatar_id":"","url":"https://api.github.com/users/sigurdm","html_url":"https://github.com/sigurdm","followers_url":"https://api.github.com/users/sigurdm/followers","following_url":"https://api.github.com/users/sigurdm/following{/other_user}","gists_url":"https://api.github.com/users/sigurdm/gists{/gist_id}","starred_url":"https://api.github.com/users/sigurdm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sigurdm/subscriptions","organizations_url":"https://api.github.com/users/sigurdm/orgs","repos_url":"https://api.github.com/users/sigurdm/repos","events_url":"https://api.github.com/users/sigurdm/events{/privacy}","received_events_url":"https://api.github.com/users/sigurdm/received_events","type":"User","site_admin":false},"created_at":"2015-12-07T07:48:09Z","updated_at":"2015-12-07T07:48:09Z","body":"Hi Lasse. Thanks for the suggestion. I believe you are looking for already exists:\r\n```\r\n/// Quantifying capability instance specifying that the reflection support\r\n/// for any given explicitly declared getter must also be given to its\r\n/// corresponding explicitly declared setter, if any.\r\nconst correspondingSetterQuantifyCapability = [...]\r\n```\r\n\r\nAbout the general note - can you give an example of how the code you imagine would look like? I'm not sure I follow exactly what you mean by \"first-class treatment\". Preferably in a new issue."}}