Illegal Assignment from List to <SObject>

Issue #908 resolved
Erik Malmberg created an issue

Hi,

I see a few posts where this is an error and you've posted it to be resolved, I'm however still receiving such an error (see image below). https://i.imgur.com/1XzmjAU.jpg Thanks in advance.

PS, Scott, you're doing a hell of a job!

Comments (6)

  1. Scott Wells repo owner

    Hi, Erik. That looks like Resource__c is not part of your offline symbol table so it's not resolving. As a result other things aren't able to resolve. Can you regenerate your OST and let me know if that doesn't solve the issue for you?

  2. Scott Wells repo owner

    So I do see Resource__c.cls in the root of the OST you provided. Is it working for you now? If not, do you mind rebuilding caches/indices one more time using either File>Invalidate Caches / Restart or Illuminated Cloud>Configure Project>Rebuild Caches and Indices followed by an IDE restart or minimally closing and reopening the project?

  3. Erik Malmberg reporter

    That actually did solve it - thanks a lot, simply awesome. On another note, do you know why the event log is not as detailed when developing in a DX Scratch Org? I only get "Push Complete" or "Push complete 0/X Components" - no error message where the issue is such as line, which component, missing semantics or so.

  4. Scott Wells repo owner

    Glad to hear that solved it. As for details on push/pull operations, take a look at the Messages view instead of the Event Log view. You should get a similar output to what you'd see directly from the sfdx CLI. When there are errors during a push you can use the Illuminated Cloud Problems view for a tree-based view of the errors. In both cases, the errors should also be hyperlinked to the source and annotated in the respective editor windows. I need to move the end-of-process notification to show on the proper tool window instead of always being on the Event Log as it automatically draws the eye to that view when it doesn't contain the real details...

  5. Scott Wells repo owner

    I'm going to resolve this for now since that seems to have addressed it for you. Feel free to reopen or log new issues if you find any other code inspection false negatives. I'm trying to pick those off as quickly as possible to provide a solid signal-to-noise ratio.

  6. Log in to comment