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
Is your enhancement request related to a problem? Please describe.
I am frustrated that when using auto-complete I cannot automatically prepend the namespaace as it often leads to bad practices on the team. It is also kind of annoying when I have to backtrack to add the namespace myself. to ensure consistency etc
Describe the solution you'd like
Have a toggle/boolean in the VsCode settings that allows auto-complete to prepend the namespace Describe alternatives you've considered
I tried enforcing it manually or making a linter to catch it, but it would honestly just be easier if I can force it
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
That sounds like a great idea, and I will include it, but you don’t have to be frustrated ;-)
It might also be a good idea to add a QuickFix that automatically handles this for the selected keywords.
And by the way, do you know the shortcut CONTROL+ALT? It shows the namespaces where they aren’t indicated. You can also enable it fully so that you won’t have to add it manually anymore.
Is your enhancement request related to a problem? Please describe.
I am frustrated that when using auto-complete I cannot automatically prepend the namespaace as it often leads to bad practices on the team. It is also kind of annoying when I have to backtrack to add the namespace myself. to ensure consistency etc
Describe the solution you'd like
Have a toggle/boolean in the VsCode settings that allows auto-complete to prepend the namespace
Describe alternatives you've considered
I tried enforcing it manually or making a linter to catch it, but it would honestly just be easier if I can force it
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: