-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False positive "Illegal assignment from List<AggregateResult> to List<AggregateResult>" #6052
Comments
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. |
Hi @PawelWozniak Thanks for reporting the issue. Could you try the steps below and see if the warnings get disappeared?
Thank you. |
Hi @mingxuanzhangsfdx I have applied the steps as suggested. Even closed and opened VSCode again, but no changes. Still, I see the same problem on the list. |
Can you run |
@daphne-sfdc Yes done that, output:
I waited a few minutes and no change, it is still shown. |
This issue has not received a response in 3 days. It will auto-close in 2 days unless a response is posted. |
Summary
I am getting the false positive error message
"Illegal assignment from List<AggregateResult> to List<AggregateResult>"
which itself is not logical as the two types are the same. There are no compile errors on save.Steps To Reproduce:
Type this code in apex class
Filed Contract_Without_Opportunity_Cnt_Number__c is a numeric value. I am searching for the highest value across all records.
Expected result
No error is shown as the two types are the same, and the compiler doesn't show errors.
Actual result
I am getting a confusing error.
Additional information
Salesforce Extension Version in VS Code: 62.14.1
Salesforce CLI Version: @salesforce/cli/2.74.6 win32-x64 node-v22.13.1
OS and version: Windows 11
VS Code version: 1.96.4
Most recent version of the extensions where this was working:
The text was updated successfully, but these errors were encountered: