{"action":"created","issue":{"url":"https://api.github.com/repos/esdoc/esdoc/issues/66","labels_url":"https://api.github.com/repos/esdoc/esdoc/issues/66/labels{/name}","comments_url":"https://api.github.com/repos/esdoc/esdoc/issues/66/comments","events_url":"https://api.github.com/repos/esdoc/esdoc/issues/66/events","html_url":"https://github.com/esdoc/esdoc/issues/66","id":104199009,"number":66,"title":"Documentation for module (Feature Request)","user":{"login":"PinkaminaDianePie","id":1625500,"avatar_url":"https://avatars.githubusercontent.com/u/1625500?v=3","gravatar_id":"","url":"https://api.github.com/users/PinkaminaDianePie","html_url":"https://github.com/PinkaminaDianePie","followers_url":"https://api.github.com/users/PinkaminaDianePie/followers","following_url":"https://api.github.com/users/PinkaminaDianePie/following{/other_user}","gists_url":"https://api.github.com/users/PinkaminaDianePie/gists{/gist_id}","starred_url":"https://api.github.com/users/PinkaminaDianePie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/PinkaminaDianePie/subscriptions","organizations_url":"https://api.github.com/users/PinkaminaDianePie/orgs","repos_url":"https://api.github.com/users/PinkaminaDianePie/repos","events_url":"https://api.github.com/users/PinkaminaDianePie/events{/privacy}","received_events_url":"https://api.github.com/users/PinkaminaDianePie/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/esdoc/esdoc/labels/Feature","name":"Feature","color":"c7def8"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":9,"created_at":"2015-09-01T06:53:37Z","updated_at":"2015-09-14T08:26:28Z","closed_at":"2015-09-14T08:26:28Z","body":"It will be great to add support of documentation for module. Ill explain the case: i have module with logicaly grouped helpers. I can use it with 2 ways. With first i need to create class with static helpers, and export it as default. Then i need to use it in this way:\r\n```javascript\r\nimport helpers from 'helpers';\r\nhelpers.method(); \r\nhelpers.const;\r\n```\r\nWith second way ill define all helpers as simple functions and export them all from my module. \r\n```javascript\r\nlet helper = function(){};\r\nexport {helper};\r\n```\r\nThen ill use it:\r\n```javascript\r\nimport * as helpers from 'helpers';\r\nhelpers.method(); \r\nhelpers.const;\r\n```\r\nBut with this way i can import only helpers i need, by their names:\r\n```javascript\r\nimport {method, const} from 'helpers';\r\nmethod(); \r\nconst;\r\n```\r\nand using them will be much easier. With static class approach i need to always use it as namespace for my methods. So if i need to export some helpers from my module i will always choose second way of exporting. But the problem of this is i can not documentate module. The only solution i found it is  defining static class and then export methods from them as one namespace. May be it will be better to provide functionality to documentate module?"},"comment":{"url":"https://api.github.com/repos/esdoc/esdoc/issues/comments/139998056","html_url":"https://github.com/esdoc/esdoc/issues/66#issuecomment-139998056","issue_url":"https://api.github.com/repos/esdoc/esdoc/issues/66","id":139998056,"user":{"login":"h13i32maru","id":985170,"avatar_url":"https://avatars.githubusercontent.com/u/985170?v=3","gravatar_id":"","url":"https://api.github.com/users/h13i32maru","html_url":"https://github.com/h13i32maru","followers_url":"https://api.github.com/users/h13i32maru/followers","following_url":"https://api.github.com/users/h13i32maru/following{/other_user}","gists_url":"https://api.github.com/users/h13i32maru/gists{/gist_id}","starred_url":"https://api.github.com/users/h13i32maru/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/h13i32maru/subscriptions","organizations_url":"https://api.github.com/users/h13i32maru/orgs","repos_url":"https://api.github.com/users/h13i32maru/repos","events_url":"https://api.github.com/users/h13i32maru/events{/privacy}","received_events_url":"https://api.github.com/users/h13i32maru/received_events","type":"User","site_admin":false},"created_at":"2015-09-14T08:26:28Z","updated_at":"2015-09-14T08:26:28Z","body":"@PinkaminaDianePie @madx Thanks for your proposal.\r\n\r\nBut I have the following policy.\r\n\r\n- ES6 code style is Class Base OOP\r\n- ESDoc mainly support class\r\n- function support is secondly\r\n- ES6 module is **file** base system\r\n\r\n```javascript\r\nfunction foo1(){}\r\nfunction foo2(){}\r\n// this does not have module name by syntax.\r\n// but this has module name by file name.\r\nexport {foo2, foo2}\r\n```\r\n\r\n- directory base navigation provides full module name\r\n  - module name confusion is reduced by it\r\n- **ESDoc must use the ones that already exist**\r\n  - code syntax and file/directory structure\r\n\r\nSo, I do not support ``@module``.\r\nSorry.\r\n"}}