Weird behavior in relationships within Nova

It sounds like you're experiencing namespace conflicts or misconfigurations in your Nova resources. Here are a few steps to troubleshoot and resolve the issue:

1. Check Namespace and Class Names: Ensure that the namespaces and class names in your Nova resources match exactly with your models. Any typo or mismatch can cause Nova to load the wrong resource.

2. Explicitly Define Relationships in Models: Make sure that the relationships in your Municipalities and Counties models are correctly defined. For example:

   namespace App\Models\Building;
   
   use Illuminate\Database\Eloquent\Model;
   
   class Municipalities extends Model
   {
       public function addresses()
       {
           return $this->hasMany(\App\Models\Building\Municipalities\Address::class);
       }
   
       // Other relationships...
   }
   
   class Counties extends Model
   {
       public function addresses()
       {
           return $this->hasMany(\App\Models\Building\Counties\Address::class);
       }
   
       // Other relationships...
   }
   

3. Define Resources in Nova: Ensure that your Nova resources are correctly defined and that the relationships are explicitly stated. For example:

   namespace App\Nova;
   
   use Laravel\Nova\Resource;
   use Laravel\Nova\Fields\HasMany;
   
   class Municipality extends Resource
   {
       public static $model = \App\Models\Building\Municipalities::class;
   
       public function fields(Request $request)
       {
           return [
               HasMany::make('Addresses', 'addresses', \App\Nova\Municipalities\Address::class),
               // Other fields...
           ];
       }
   }
   
   class County extends Resource
   {
       public static $model = \App\Models\Building\Counties::class;
   
       public function fields(Request $request)
       {
           return [
               HasMany::make('Addresses', 'addresses', \App\Nova\Counties\Address::class),
               // Other fields...
           ];
       }
   }
   

4. Check Resource Registration: Ensure that your resources are correctly registered in NovaServiceProvider. For example:

   use App\Nova\Municipality;
   use App\Nova\County;
   
   public function resources()
   {
       Nova::resources([
           Municipality::class,
           County::class,
           // Other resources...
       ]);
   }
   

5. Clear Cache: Sometimes, Nova or Laravel caches can cause issues. Clear your application cache and config cache:

   php artisan cache:clear
   php artisan config:clear
   php artisan route:clear
   php artisan view:clear
   

6. Check for Duplicate Resource Names: Ensure that there are no duplicate resource names or conflicting resource names in your Nova resources.

By following these steps, you should be able to resolve the issue of Nova loading the wrong resource. If the problem persists, consider providing more specific details or error messages to further diagnose the issue.