{"action":"reopened","issue":{"url":"https://api.github.com/repos/angular/clutz/issues/275","repository_url":"https://api.github.com/repos/angular/clutz","labels_url":"https://api.github.com/repos/angular/clutz/issues/275/labels{/name}","comments_url":"https://api.github.com/repos/angular/clutz/issues/275/comments","events_url":"https://api.github.com/repos/angular/clutz/issues/275/events","html_url":"https://github.com/angular/clutz/issues/275","id":149162887,"number":275,"title":"No types generated for proto nested enums ","user":{"login":"rehmsen","id":29040,"avatar_url":"https://avatars.githubusercontent.com/u/29040?v=3","gravatar_id":"","url":"https://api.github.com/users/rehmsen","html_url":"https://github.com/rehmsen","followers_url":"https://api.github.com/users/rehmsen/followers","following_url":"https://api.github.com/users/rehmsen/following{/other_user}","gists_url":"https://api.github.com/users/rehmsen/gists{/gist_id}","starred_url":"https://api.github.com/users/rehmsen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rehmsen/subscriptions","organizations_url":"https://api.github.com/users/rehmsen/orgs","repos_url":"https://api.github.com/users/rehmsen/repos","events_url":"https://api.github.com/users/rehmsen/events{/privacy}","received_events_url":"https://api.github.com/users/rehmsen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-04-18T14:12:46Z","updated_at":"2016-04-19T14:13:13Z","closed_at":null,"body":"For a proto file with a nested enum\r\n\r\n    message Foo {\r\n      enum Bar {\r\n         BAZ = 0;\r\n      }\r\n\r\n      Bar bar = 1;\r\n    }\r\n\r\nClutz skips the nested enum and generates\r\n\r\n    interface Foo {\r\n      bar : ಠ_ಠ.clutz.Foo.Bar ;\r\n    }\r\n\r\nBut no type for Bar. The Typescript compiler then complains:\r\n\r\n> Module 'ಠ_ಠ.clutz.' has no exported member 'Foo'.\r\n\r\nIn my own code I can move the enum out of the message, but this is also happening for protos that are pulled in by my dependencies, where this is more tricky. \r\nNot sure if this is only broken for enums or for any nested message.\r\n\r\nAny workaround? Any timeline for getting this fixed?"}}