{"action":"closed","issue":{"url":"https://api.github.com/repos/sigmundch/DEP-member-interceptors/issues/8","labels_url":"https://api.github.com/repos/sigmundch/DEP-member-interceptors/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/sigmundch/DEP-member-interceptors/issues/8/comments","events_url":"https://api.github.com/repos/sigmundch/DEP-member-interceptors/issues/8/events","html_url":"https://github.com/sigmundch/DEP-member-interceptors/issues/8","id":65503593,"number":8,"title":"More rationale for using annotation syntax","user":{"login":"munificent","id":46275,"avatar_url":"https://avatars.githubusercontent.com/u/46275?v=3","gravatar_id":"","url":"https://api.github.com/users/munificent","html_url":"https://github.com/munificent","followers_url":"https://api.github.com/users/munificent/followers","following_url":"https://api.github.com/users/munificent/following{/other_user}","gists_url":"https://api.github.com/users/munificent/gists{/gist_id}","starred_url":"https://api.github.com/users/munificent/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/munificent/subscriptions","organizations_url":"https://api.github.com/users/munificent/orgs","repos_url":"https://api.github.com/users/munificent/repos","events_url":"https://api.github.com/users/munificent/events{/privacy}","received_events_url":"https://api.github.com/users/munificent/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-31T17:25:50Z","updated_at":"2015-03-31T20:13:34Z","closed_at":"2015-03-31T20:13:34Z","body":"To me, the biggest reason to use annotation syntax for interceptors is that it lets a library *encapsulate* the usage of interception. My awesome framework may use `@foo` as a regular annotation in 1.2.3 and then switch to making `@foo` an interceptor in 1.3.0 without breaking my users or even requiring them to know."}}