Visual Studio Code - Intelphense vs Intellisense |
1. For the service(), it has a documented return type of mixed so intelephense/intellisense cannot intelligently guess what specific object you are creating when you use that. I see 2 alternatives for that:
a. Inline annotate the variable $email PHP Code: /** var \CodeIgniter\Email\Email $email */ b. Use the Services class to get specific documentation. PHP Code: use Config\Services; 2. For the Model/Builder, there exists a "@mixin" relationship for the two. The Model has a __call method that delegates unknown method calls to the Builder if the Builder has those methods defined. That's why you can call where(), a Builder method, in the context of a Model. Unfortunately, there's no straightforward way to make the 2 extensions understand this relationship. Support for this may be complex for them. What I can see as a possible solution (although not 100% spot on solution) is to use the "@method" annotation in the class docblock of Model. But as I said that solution is a patch not a cure. I'm using VS Code so I am aware of these concerns. ![]() |
Messages In This Thread |
Visual Studio Code - Intelphense vs Intellisense - by Corsari - 04-05-2021, 02:39 AM
RE: Visual Studio Code - Intelphense vs Intellisense - by atifriazmughal - 08-11-2021, 06:25 PM
RE: Visual Studio Code - Intelphense vs Intellisense - by paliz - 08-12-2021, 01:07 AM
RE: Visual Studio Code - Intelphense vs Intellisense - by Corsari - 08-31-2021, 04:45 AM
RE: Visual Studio Code - Intelphense vs Intellisense - by wdeda - 08-31-2021, 02:47 PM
RE: Visual Studio Code - Intelphense vs Intellisense - by Corsari - 08-31-2021, 10:21 PM
RE: Visual Studio Code - Intelphense vs Intellisense - by InsiteFX - 09-01-2021, 12:19 AM
RE: Visual Studio Code - Intelphense vs Intellisense - by wdeda - 09-01-2021, 04:43 AM
RE: Visual Studio Code - Intelphense vs Intellisense - by paulbalandan - 09-02-2021, 07:21 AM
|