12
Wombat
126d

Laravels error reporting is sometimes fucking useless. Yesterday it wrote into the logs "class foo doesn't exist". I triple checked the including of this class. Checked the namespaces. Checked the classnames. Everything was ok.
Today I removed the content of this particular class, which returned an array. And the error was gone...

After further search I realized I was missing commas within the array deceleration...

Why the fuck you don't just tell me this????!?

Comments
  • 1
    I've noticed this getting worse with the later versions of Laravel.

    In a recent project I was receiving a class doesn't exist error and it turned out that a method declared in a repository didn't match the definition in the interface!
  • 1
    try to remove a composer cached file 😑
  • 1
    @lainga9 can't relate to older versions of Laravel. But for the latest version error reporting sucks.

    @raldo94 thanks, I will try that. Though I can't believe this would make Laravel improve it's logging.
  • 0
    I believed that I was simply to retarded to understand some of the error messages...

    So it turns out me and laravel are retarded sometimes ¯\_ (ツ) _/¯
Your Job Suck?
Get a Better Job
Add Comment