Hello @dwaynecharrington @fkleuver ,
I know you guys are working on LSP, which from what I’ve been reading, is pretty exciting I have to say!
I have a question that’s really a matter of curiosity. I’m in the process, as I migrate our Au 1.0 app to 2.0, of moving to global registration (getting away from decorator-based registration). It would be nice if, at the point of the export class SomeClass line, I could be advised with details on the global registration (if there’s no registration decorator on the class).
GitLens offers all sorts of inline information available upon hover, for example.
Is this something that would be within the bounds of the capabilities of LSP? Perhaps I could write a plugin that surfaces the global registration information right at the class definition?
I’m just tired of going back and forth between main.js, which I keep as a pinned tab.
Just a question…and a thought…
1 Like
It’s already available.
Aurelia extension is able to see all the resources registered, in many shape and side, even one that comes from 3rd party packages as well. For example, @aureliaaurelia/router as a 3rd party package:
1 Like
Hello @bigopon ,
I have seen that, yes, which is awesome by the way!
I was thinking about something more immediate. Consider the following screenshot from my TsiMessageBus implementation:
It would be nice if we could get those GitLens-style inline messages (you can see above where it starts “You, 2 months ago…”) One of the advantages of decorator-based registration is the immediacy of the information: I don’t have to refer back to main to check my global registrations. It would be nice if we could get some kind of hover feedback or inline feedback.
I was just wondering if LSP brings that kind of flexibility in terms of plugin development. And, BTW, we’re just talking here. I don’t mean for this to be a feature suggestion…and least not at this time.
It’s just that sometimes I feel like VS Code’s power isn’t being fully leveraged—in general, not necessarily in the context of Aurelia.
