Replies: 1 comment
-
Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming session. We prioritize feature requests with more upvotes and comments. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
If an LWC component has a underscore in its name it is not possible to click through to this component when hovering over it in a html file. It is possible to do this for LWC components without underscores within the name. This means having to search for the component manually usually by copying its name and correcting the case. We use underscores for most of our components to indicate the particular product area a component belongs i.e. tm_filterPanel.
Describe the solution you'd like
LWC components with underscores should be able to utilise all of the html smart features such as click through and hover to view api properties in the same way as components without underscores.
Additional context
From these two screenshots you can see that for the adaptiveDefaulter you have click through but for the component with a underscore it is not possible to do that. Note that adaptiveDefaulter in this case had no markup file with the same name which is why the click through went directly to the js file, if it had html file (with the same name) clicking through would have opened a panel with an option for the js and html file each can then be clicked through.
Beta Was this translation helpful? Give feedback.
All reactions