Replies: 2 comments
-
Thank you @irvinsci for sending the feature request. We will let you know if we will implement the feature! |
Beta Was this translation helpful? Give feedback.
-
Hi @irvinsci, Those standard Apex snippets come from the As a workaround, with the VSCode: File > Preferences > Configure Snippets > New Global Snippets file..., you can create an {
"@AuraEnabled annotation": {
"prefix": "@AuraEnabled",
"body": [
"@AuraEnabled"
],
"description": "@AuraEnabled annotation only"
},
"@AuraEnabled variable": {
"prefix": "@AuraEnabled variable",
"body": [
"@AuraEnabled",
"public ${1:varType} ${0:varName};"
],
"description": "Basic @AuraEnabled class variable"
},
} Unfortunately, it doesn't seem to allow overriding/shadowing the default Apex snippet for the The
|
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
The
@AuraEnabled
auto complete does not fit all use cases. When it is used in the wrong use case, I end up having to battle my muscle memory to not use the auto complete to populate incorrect code for my use case.Describe the solution you'd like
Remove this auto complete suggestion. Or otherwise expose all auto complete suggestions in a settings page that users can customize.
Describe alternatives you've considered
I am tempted to disable this extension everytime this happens.
Additional context
See that we use
@AuraEnabled
to describe variablesSee how the
@AuraEnabled
auto complete always shows up in this case even when it is inappropriateSee how any accidental key stroke can populate multiple unwanted lines require multiple keystrokes to cleanup
Beta Was this translation helpful? Give feedback.
All reactions