{"action":"closed","issue":{"url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/4339","repository_url":"https://api.github.com/repos/jhipster/generator-jhipster","labels_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/4339/labels{/name}","comments_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/4339/comments","events_url":"https://api.github.com/repos/jhipster/generator-jhipster/issues/4339/events","html_url":"https://github.com/jhipster/generator-jhipster/issues/4339","id":183380978,"number":4339,"title":"[FEATURE] jhipster:entity - Support grouping of entities into 'modules'","user":{"login":"HemanthD","id":16206433,"avatar_url":"https://avatars.githubusercontent.com/u/16206433?v=3","gravatar_id":"","url":"https://api.github.com/users/HemanthD","html_url":"https://github.com/HemanthD","followers_url":"https://api.github.com/users/HemanthD/followers","following_url":"https://api.github.com/users/HemanthD/following{/other_user}","gists_url":"https://api.github.com/users/HemanthD/gists{/gist_id}","starred_url":"https://api.github.com/users/HemanthD/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HemanthD/subscriptions","organizations_url":"https://api.github.com/users/HemanthD/orgs","repos_url":"https://api.github.com/users/HemanthD/repos","events_url":"https://api.github.com/users/HemanthD/events{/privacy}","received_events_url":"https://api.github.com/users/HemanthD/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-10-17T10:34:14Z","updated_at":"2016-10-17T14:24:24Z","closed_at":"2016-10-17T14:24:23Z","body":"##### **Overview of the issue**\r\n\r\nSupport a sub-package/module name for entities which can be used to group entities and their back-end/front-end code.\r\n\r\n##### **Motivation for or Use Case**\r\n\r\nWhen the monolith app has many entities, it'd be helpful to be able to group them into logical 'modules'. This will also help in being able to reuse the same name for similar entities in different modules.\r\n\r\nThe request is not change the package structure itself, but to be able to support an additional leaf-level package such as domain._module1_.entity1.java, web.rest._module2_.entityResource.java, _added_entity_module4_Entity4.xml, app/entities/_module3_/*.js etc.\r\n\r\nThe --table-name, in some ways, support the database table 'grouping' by being able to provide an overridden table name with specific prefixes.\r\n\r\n##### **Reproduce the error**\r\n\r\nNA\r\n\r\n##### **Related issues**\r\n\r\nSimilar requests have not been reported - but there have been feature requests for changing the package structure #4125, #3496 etc.\r\n\r\n##### **Suggest a Fix**\r\n\r\nAn optional parameter --module-name can be accepted during jhipster:entity which will redirect/read the json from .jhipster/_module_/entity.json and will also store the module-name within the json. This can be used as a suffix to suitably modify the package name in the templates.\r\n\r\n\r\n##### **JHipster Version(s)**\r\n\r\n3.8.0\r\n\r\n##### **JHipster configuration, a `.yo-rc.json` file generated in the root folder**\r\n\r\nNA\r\n\r\n##### **Entity configuration(s) `entityName.json` files generated in the `.jhipster` directory**\r\n\r\nNA\r\n\r\n##### **Browsers and Operating System**\r\n\r\nWindows 10 with MySQL 5.7.15 and Chrome\r\n"}}
{"actor":{"display_login":"jdubois"}}