Replies: 2 comments
-
Hi again, This is an idea I already have for quite some time, and there would be many other great ideas for enhancing generation like this one. Note however that the extension is just a graphic interface for existing schematics, it does not generate anything by itself. While it would not be impossible to do generation directly inside the extension code, it would clearly be better in a separate tool, ie. schematics, that could complement the extension (or even be included directly in the extension, but still a separate tool). The main issue is time, or more exactly money. This extension is already hundreds hours of unpaid work, all by myself (and I have another popular Angular tool to maintain). I've reached the limit to what I can do unpaid, and currently I only have one sponsor. Your GitHub profile suggests that you work on your own, so I can't ask you if your company would sponsor this work, but clearly with the adequate support I could make a whole architecture tool, including this idea. Moving this to the new GitHub "Discussions" tab (where you can continue the discussion), as it is not an issue. |
Beta Was this translation helpful? Give feedback.
-
Hi @andy-bond, for information, this is available in the Pro edition. |
Beta Was this translation helpful? Give feedback.
-
Checks before posting an issue
ng g component hello
in the VS Code Terminal inside my project, and it worksConfiguration
ng version
):Description of the Feature
It is a pretty common practice in Angular to use
index.ts
(barrel) files to re-export services/components/etc to make importing them easier in other areas of the application.For example, I may have a
services
folder with auser.service.ts
and apermissions.service.ts
. Rather than import them separately in a component that needs both services, I generally export both services in theservices/index.ts
file like so:Some people may prefer to use the
*
method instead, so perhaps that could be an option as well for this feature:Both methods of exporting allow me to easily import both services in a component (ex:
components/profile.component.ts
) like so:Additions to the Extension
export { generated-item } from generated-item-file
inindex.ts
(if one exists in the context)generated-item
in the module after step 1 (that way it is imported via barrel file)export * from generated-item-file
if that line doesn't already exist in theindex.ts
(if one exists in the context)index.ts
if none existsHopefully I was clear in explaining what I would like to have the extension automate for me. Happy to explain further if I wasn't clear enough.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions