⚠️ Potential issue | 🔴 Critical

The as any cast masks a real bug: PropertyGrid ignores the passed props.

Per the relevant snippet from PropertyGrid.tsx (lines 128-136), the component accepts no props and renders mockProperties directly. The passed properties and onLoadMore props on Line 102 are silently ignored, meaning:

• Filtering/sorting logic (Lines 35-58) has no effect on rendered output
• Pagination via loadNextPage doesn't work
• Users always see hardcoded mock data regardless of filters

The as any cast hides the TypeScript error that would have caught this.

// In PropertyGrid.tsx
interface PropertyGridProps {
  properties: Property[];
  onLoadMore?: () => void;
}

export const PropertyGrid = ({ properties, onLoadMore }: PropertyGridProps) => {
  return (
    <div className="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 xl:grid-cols-4 gap-8">
      {properties.map((property) => (
        <PropertyCard key={property.id} property={property} />
      ))}
      {onLoadMore && (
        <button onClick={onLoadMore}>Load More</button>
      )}
    </div>
  );
};

-  // Alias para evitar el error de IntrinsicAttributes
-  const Grid = PropertyGrid as any;
   ...
-  <Grid properties={visibleProperties} onLoadMore={loadNextPage} />
+  <PropertyGrid properties={visibleProperties} onLoadMore={loadNextPage} />

Also applies to: 102-102

In `@apps/web/src/app/search/page.tsx` around lines 78 - 79, PropertyGrid
currently ignores passed props because it has no props type and renders
mockProperties; update PropertyGrid to accept a props interface (e.g.,
PropertyGridProps with properties: Property[] and optional onLoadMore: () =>
void), use those props inside the component to map properties to PropertyCard
and call/render onLoadMore for pagination, then remove the "as any" alias in
page.tsx so the real typing error surfaces and the caller passes its properties
and onLoadMore correctly to PropertyGrid.