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
Suggestions do not work as expected in Apex(maybe in js/html/css as well) when metadata has prefixes with number. For example we are using "TEST1_" prefixes in all our metadata (Classes/Objects/LWCs and etc.) to represent that it is metadata of the "TEST1" project.
Steps To Reproduce:
Create Apex Class/SObject/(Anything what can be suggested as auto-complete in Apex) and name it with number in the middle (for example "prefix1TestclassName").
Start typing begining of the created Metadata name, stop when number is typed and wait for suggestions. Suggestions is showing this metadata for autocomplete. (for example "prefix1TestclassName" exists, typing "prefix1" will show "prefix1TestclassName" as suggestion.)
Add next symbol of created Metadata name. (for example "prefix1TestclassName" exists, you will type "prefix1T")
Delete this symbol. (for example "prefix1TestclassName" exists, you will type "prefix1T" and then after deleting last symbol it will be "prefix1").
Expected result
Suggestions is showing this metadata for autocomplete.
Actual result
Suggestions is not showing this metadata for autocomplete
Additional information
It doesn't recognize begining of the typed text if there is number in metadata name it tries to suggest and then you delete symbols after number. So, it means not only that it doesn't show suggestions after deleting of those symbols, but it also means that if after that you try to type middle of the metadata name, then It will suggest to insert its full name without replacing previously typed begining of the name:
Start typing
Delete last symbol and type it back. In this case "T" have been deleted and typed back.
Continue typing of required class until expected suggestion appears again
Apply suggestion. Expected "pref1TestClassWithoutUnderscore", but get "pref1pref1TestClassWithoutUnderscore"
Salesforce Extension Version in VS Code: v62.5.1
Salesforce CLI Version: 2.67.7
OS and version: Windows 11 Enterprise 10.0.26100
VS Code version: 1.95.3
Most recent version of the extensions where this was working: It has never worked.
The text was updated successfully, but these errors were encountered:
Paul-Kalynyn
changed the title
Apex Code suggestions works unexpected when suggestion contains number in the sf name
Apex Code suggestions works unexpected when suggestion contains number in the name
Dec 4, 2024
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.
Summary
Suggestions do not work as expected in Apex(maybe in js/html/css as well) when metadata has prefixes with number. For example we are using "TEST1_" prefixes in all our metadata (Classes/Objects/LWCs and etc.) to represent that it is metadata of the "TEST1" project.
Steps To Reproduce:
Expected result
Suggestions is showing this metadata for autocomplete.
Actual result
Suggestions is not showing this metadata for autocomplete
Additional information
It doesn't recognize begining of the typed text if there is number in metadata name it tries to suggest and then you delete symbols after number. So, it means not only that it doesn't show suggestions after deleting of those symbols, but it also means that if after that you try to type middle of the metadata name, then It will suggest to insert its full name without replacing previously typed begining of the name:
Start typing
Delete last symbol and type it back. In this case "T" have been deleted and typed back.
Continue typing of required class until expected suggestion appears again
Apply suggestion. Expected "pref1TestClassWithoutUnderscore", but get "pref1pref1TestClassWithoutUnderscore"
Salesforce Extension Version in VS Code: v62.5.1
Salesforce CLI Version: 2.67.7
OS and version: Windows 11 Enterprise 10.0.26100
VS Code version: 1.95.3
Most recent version of the extensions where this was working: It has never worked.
The text was updated successfully, but these errors were encountered: