Hi,

I have updated to the latest version (1.84.20575) and it seems to have broken intellisense again.

It's quite frustrating that this has happened to me a few times now when updating to the latest version.

Is there a way of getting to the root cause, or is there some button you can create that I can run that will do a check of all settings, reset any caches or whatever is required to restore functionality?

FYI, I have reverted to version PHP.VS.1.83.20414.2022 and the Intellisense works again.

Regards,

John

JohnWhiteman Thank you for reporting this. We'll try to fix it asap and avoid a similar issue in future.

    JohnWhiteman I think there is a corrupted cache, the autocomplete should work in 1.84 and composer package "filament/tables": "^2.17" correctly:

    Please try to delete the following directory, and re-load your project:

    %localappdata%\DEVSENSE\packages-cache

    If it solves the issue, we'll try to fix it within the next update.

      JohnWhiteman even after reloading the project?

      Do you have a tooltip over ::make( ? or tooltip over TextColumn ?

        Sorry,

        I don't have the time to reinstall the plug-in to try again and then revert to the old one.

        All I can tell you is that the 1.83.20414 version works and the latest doesn't for some reason.

        What do you mean by 'reloading the project'? I am currently just installing the new version and opening the project as normal.

        Is there something else I need to do?

          JohnWhiteman I understand, I appreciate the information.

          Add re-loading - just closing and opening the Solution or Visual Studio.

          I'll do more tests hopefully reproducing the issue.

            Let me know if you need the code base or if you want to connect to my PC for zoom etc.
            You have my email address to contact me directly. Cheers

              Re: re-loading...

              When I install/uninstall the extension, Visual Studio always needs to exit to do it, so I guess it has been reloading?

              Anyway, just FYI, cheers :)

              JohnWhiteman Thank you, John. I appreciate it. I'll try to reproduce the issue locally, and if I'm hopeless, I'd be happy to contact you via email.

              Yes, exiting VS counts as a reload :) Anyways; deleting that folder should fix the issue - I'm still looking at it.

                Write a Reply...