You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@SylvainMarty Thank you for reporting this feature request in KartanHQ/intellij-nestjs/ repo . I'm launching a NestJS plugin. I'm planning to include this functionality into this plugin. Unfortunately, the maintainer of KartanHQ/intellij-nestjs/ repository does not have enough bandwidth to add more features or accept PRs at this time.
Is your feature request related to a problem? Please describe.
We use CQRS (@nestjs/cqrs) extensively in our NestJS monorepo project and many of our developers complains about navigation between CQRS files being not very efficient nor natural.
The main complaint was how slow it was to navigate from the usage of Command/Query to the dedicated Handler which does the work under the hood.
Here is an "example" of the problem:
// 1. The dev see this code somwhere:constcommand=newMyCommand();awaitthis.commandBus.execute(command);// 2. The dev wants to go to the handler which implement the command logic// First, it needs to do "Go to implementation" (Ctrl + B) to see the command class definition// Then it needs to "Go to Declaration and usage" (Ctrl + B) to see all the usages and select the one which relates to the handlerSinceourcode is mostlyCQRSimplementations,thismechanicneedstohappenalotoftimeandisnotveryefficient.
Aside that, we really like CQRS, we just want to be more efficient using it. :-)
Describe the solution you'd like
I'm not sure what the best solution would be but I was thinking that it would be easier to have a shortcut/option to go to the implementation of a command (aka its handler).
I think it may be possible to get this information since all commands are references by its handler in the @CommandHandler(MyCommand) annotation.
Describe alternatives you've considered
I searched online to see if there were any plugins or shortcut in Intellij based IDE to achieve this but so far, I only found a feature specific to Resharper: Resharper > Navigate To > Consuming APIs.
Sadly this feature is not present on our IDE (PHPStorm).
Additional context
I never developed plugins for Intellij but I have experience in Java/Kotlin and I'm interested in submitting a PR if you think it can be handled by this plugin. 😃
The text was updated successfully, but these errors were encountered:
@SylvainMarty Thank you for reporting this feature request in
KartanHQ/intellij-nestjs/
repo . I'm launching a NestJS plugin. I'm planning to include this functionality into this plugin. Unfortunately, the maintainer ofKartanHQ/intellij-nestjs/
repository does not have enough bandwidth to add more features or accept PRs at this time.Is your feature request related to a problem? Please describe.
We use CQRS (@nestjs/cqrs) extensively in our NestJS monorepo project and many of our developers complains about navigation between CQRS files being not very efficient nor natural.
The main complaint was how slow it was to navigate from the usage of Command/Query to the dedicated Handler which does the work under the hood.
Here is an "example" of the problem:
Aside that, we really like CQRS, we just want to be more efficient using it. :-)
Describe the solution you'd like
I'm not sure what the best solution would be but I was thinking that it would be easier to have a shortcut/option to go to the implementation of a command (aka its handler).
I think it may be possible to get this information since all commands are references by its handler in the
@CommandHandler(MyCommand)
annotation.Describe alternatives you've considered
I searched online to see if there were any plugins or shortcut in Intellij based IDE to achieve this but so far, I only found a feature specific to Resharper: Resharper > Navigate To > Consuming APIs.
Sadly this feature is not present on our IDE (PHPStorm).
Additional context
I never developed plugins for Intellij but I have experience in Java/Kotlin and I'm interested in submitting a PR if you think it can be handled by this plugin. 😃
The text was updated successfully, but these errors were encountered: