@vincej Illuminate\Support\Facades\Input fails because of the way Laravel handles Facades. When you call the facade with a static method, it will instantiate an object for the facade and call the method with it, the non static one.

PHPStorm does not know how to react to this because it is handled at run time. IDE-HELPER by @Barryvdh generates static methods in a separate file to allow us to use "Intellisense" on our code.

Facades are namespaced too, so Input is not really Input, but \Input. Adding the use statement avoids the need to use a fully-qualified name (\Input).

@jimmck @Francismori7

Many thanks for all your help !!

I still have not swapped out the Barry plugin for the "Native" Daniel plugin. Would that help do you think ?

I found whereId in Query Builder: http://laravel.com/docs/5.0/queries#advanced-wheres

I try to avoid Eloquent when ever I can. I'm old school and would prefer to write raw SQL if I could ( but can't very well L5)

I'm now down to only 3-4 warnings .. so a vast improvement. I have use DB on my file. Regardless, the few I have left are all related to Query Builder:

@vincecj

Go on 'status' and press ALT+RETURN, you'll get a list of stuff to do - normally it's a PHP inspection that fails, you can disable that inspection. I see nothing that would do that though.

@jimmck By the way, what's your color scheme? I NEED that template!

@Francismori7

Did as you suggested. The error is an "unidentified callback".

re colour schemes: did you mean Jim or me ? Jim I don't think has shared a colour scheme except for on his setting dialogue.

@vincecj and @Francismori7

Hi, Hey Vince glad to hear things are better. First I have nothing against Eloquent. I have 20+ years using and building various database access classes/frameworks. When I wanted to learn PHP I ported a much loved Java SQL library created by a company named Weblogic. They built one of the first application servers in pure Java. I use that for all my MySQL work. Vince I have been looking at the methods not found quite intently. As I explore learning Laravel and increasing my PHP knoweledge using Storm as a tool. I am building a Mongo Document framework and have quite a few Magic functions popping up. Storm does not like them and when I try to disable those inspections it blows up the Storm EAP. But yes Vince as you also found, the Builder class does a lot of the actual 'method materilization'. And if you look at the __call magic methods you cab see where Laravel builds them. I use the Darcula color scheme it ships with Storm. I think the JetBrains team is close to Vlad's old stomping ground. Vince I am going check out Dainels stuff.

Oh BTW, Mac developers check Skitch. Its a nice Screen Grabber/Annotator. Read about in July net Magazine.

@vincej Have you tried the model option for IDE builder?

Check out doc. I don't have any actual Models, you point it to your model dir and it builds doc. From what I read it defaults to App/models.

@vincej Ah. Yes Daniel is the Laravel Plugin. Yes I have that enabled. It does not find additional methods. In the latest EAP it blows up when I try to point it to the projects view directory.

I remember Weblogic ! They were bought by Oracle - oh the joys of being old :o)

I don't understand what you mean by:

Have you tried the model option for IDE builder?

@vincej Sorry I thought I posted the link. Check out IDE Helper doc.

https://github.com/barryvdh/laravel-ide-helper

And Yes, Oracle then Gobbled up by BEA. It was a sad day when the Lead Rep called with the news.