I believe that I have found the problem and the possible fix (for my particular project!) although I have yet to modify all of my project.
Prior to udating to build 6033 I had used the following format for some of my classes within namespaces.
<?php
namespace App\Section\Module\ModuleName;
class ModuleName{
private static $instance = null;
private function __construct(){}
static function get_instance(){
if(self::$instance == null) self::$instance = new self();
return self::$instance;
}
}
|
Referencing the above class:
use \App\Section\Module\ModuleName\ModuleName as Module;
Module::get_instance()->method();
|
As you will note a double use of the ModuleName ! This worked fine for me until I udated to build 6033. Since update I have had th ebazzar issues that I described in my initial post on this issue.
Changed namespace class format within my framework to:
namespace App\Section\Modules\ModuleName;
class Obj_ModuleName{
.. etc
}
|
Now brings back all of my code completion functionality:
use \App\section\Modules\ModuleName\Obj_ModuleName as Module;
Module::get_instance()->method();
|
Is working the way it should.
So prior to build 6033 I could have a class with the same name as the namspace that it was in. Now it would seem that a class can not be named the same as the namespace that it is in.
To be honest it makes for better code readability and based on my own experience I would recomend this approach.
My framework has quite an elaborate namespace structure and as such many may not see the issues that I have, but the above does seem to have got rid of my IDE code completion problems.
I would be interrested to hear from NuSphere staff on this one.