mirror of
https://github.com/pacnpal/thrillwiki_laravel.git
synced 2025-12-20 05:51:09 -05:00
Add models, enums, and services for user roles, theme preferences, slug history, and ID generation
This commit is contained in:
pacnpal
168
memory-bank/activeContext.md
Normal file
168
memory-bank/activeContext.md
Normal file
@@ -0,0 +1,168 @@
|
||||
# Current Development Context
|
||||
|
||||
## Active Task
|
||||
Converting ThrillWiki from Django to Laravel+Livewire
|
||||
|
||||
## Current Phase
|
||||
Parks and Areas Management Implementation
|
||||
|
||||
## Progress
|
||||
|
||||
### Completed
|
||||
1. ✅ Set up Laravel project structure
|
||||
2. ✅ Create user management migrations:
|
||||
- Extended users table with required fields
|
||||
- Created profiles table
|
||||
3. ✅ Created User Management Models:
|
||||
- Enhanced User model with roles and preferences
|
||||
- Created Profile model with avatar handling
|
||||
4. ✅ Implemented User Profile Management:
|
||||
- Created ProfileComponent Livewire component
|
||||
- Implemented profile editing interface
|
||||
- Added avatar upload functionality
|
||||
5. ✅ Created Base Infrastructure:
|
||||
- ParkStatus enum with status display methods
|
||||
- IdGenerator service for consistent ID generation
|
||||
6. ✅ Implemented Slug History System:
|
||||
- Created HasSlugHistory trait
|
||||
- Implemented SlugHistory model
|
||||
- Set up polymorphic relationships
|
||||
- Added slug generation and tracking
|
||||
7. ✅ Implemented Operator/Manufacturer System:
|
||||
- Created migrations for operators and manufacturers
|
||||
- Implemented Operator model with park relationships
|
||||
- Implemented Manufacturer model with ride relationships
|
||||
- Added statistics tracking methods
|
||||
8. ✅ Implemented Parks System:
|
||||
- Created migrations for parks and areas
|
||||
- Implemented Park model with status handling
|
||||
- Implemented ParkArea model with scoped slugs
|
||||
- Added relationships and statistics tracking
|
||||
9. ✅ Created Parks Management Interface:
|
||||
- Implemented ParkFormComponent for CRUD
|
||||
- Created ParkListComponent with filtering
|
||||
- Added responsive grid layouts
|
||||
- Implemented search and sorting
|
||||
10. ✅ Created Park Areas Management:
|
||||
- Implemented ParkAreaFormComponent
|
||||
- Created ParkAreaListComponent
|
||||
- Added area filtering and search
|
||||
- Implemented area deletion
|
||||
11. ✅ Implemented Area Organization:
|
||||
- Added position and parent_id fields
|
||||
- Created drag-and-drop reordering
|
||||
- Implemented nested area support
|
||||
- Added position management
|
||||
- Created move functionality
|
||||
12. ✅ Implemented Area Statistics:
|
||||
- Added statistics fields to areas
|
||||
- Created HasAreaStatistics trait
|
||||
- Implemented statistics component
|
||||
- Added visual data display
|
||||
- Created historical tracking
|
||||
13. ✅ Implemented Statistics Rollup:
|
||||
- Added park-level statistics
|
||||
- Created HasParkStatistics trait
|
||||
- Implemented rollup service
|
||||
- Added transaction safety
|
||||
- Created event handlers
|
||||
14. ✅ Implemented Statistics Caching:
|
||||
- Created caching service
|
||||
- Added cache invalidation
|
||||
- Implemented cache warming
|
||||
- Added performance monitoring
|
||||
- Created error handling
|
||||
|
||||
### In Progress
|
||||
1. [ ] Location System Implementation
|
||||
- Model structure design
|
||||
- Polymorphic relationships
|
||||
- Map integration
|
||||
- Location selection
|
||||
|
||||
### Next Steps
|
||||
1. Location System
|
||||
- [ ] Create location model
|
||||
- [ ] Add polymorphic relationships
|
||||
- [ ] Implement geocoding service
|
||||
- [ ] Create map component
|
||||
- [ ] Add location selection
|
||||
- [ ] Implement search
|
||||
- [ ] Add clustering
|
||||
- [ ] Create distance calculations
|
||||
|
||||
2. Performance Optimization
|
||||
- [ ] Implement query caching
|
||||
- [ ] Add index optimization
|
||||
- [ ] Create monitoring tools
|
||||
- [ ] Set up profiling
|
||||
|
||||
## Technical Decisions Made
|
||||
|
||||
### Recent Implementations
|
||||
|
||||
1. Statistics Caching Design
|
||||
- Service-based architecture
|
||||
- Hierarchical caching
|
||||
- Automatic invalidation
|
||||
- Performance monitoring
|
||||
|
||||
2. Cache Management
|
||||
- 24-hour TTL
|
||||
- Batch processing
|
||||
- Error handling
|
||||
- Logging system
|
||||
|
||||
3. Performance Features
|
||||
- Efficient key structure
|
||||
- Optimized data format
|
||||
- Minimal cache churn
|
||||
- Memory management
|
||||
|
||||
### Core Architecture Patterns
|
||||
|
||||
1. Model Organization
|
||||
- Base models with consistent traits
|
||||
- Enum-based status handling
|
||||
- Automatic statistics updates
|
||||
- Slug history tracking
|
||||
|
||||
2. Data Relationships
|
||||
- Operators own parks
|
||||
- Parks contain areas
|
||||
- Areas can nest
|
||||
- Statistics rollup
|
||||
|
||||
## Notes and Considerations
|
||||
1. Need to research map providers
|
||||
2. Consider caching geocoding results
|
||||
3. May need clustering for large datasets
|
||||
4. Should implement distance-based search
|
||||
5. Consider adding location history
|
||||
6. Plan for offline maps
|
||||
7. Consider adding route planning
|
||||
8. Need to handle map errors
|
||||
9. Consider adding location sharing
|
||||
10. Plan for mobile optimization
|
||||
11. Consider adding geofencing
|
||||
12. Need location validation
|
||||
|
||||
## Issues to Address
|
||||
1. [ ] Configure storage link for avatars
|
||||
2. [ ] Add font for letter avatars
|
||||
3. [ ] Implement email verification
|
||||
4. [ ] Add profile creation on registration
|
||||
5. [ ] Set up slug history cleanup
|
||||
6. [ ] Implement ride count updates
|
||||
7. [ ] Add status change tracking
|
||||
8. [ ] Add statistics caching
|
||||
9. [ ] Implement park galleries
|
||||
10. [ ] Add position validation
|
||||
11. [ ] Implement move restrictions
|
||||
12. [ ] Add performance monitoring
|
||||
13. [ ] Create statistics reports
|
||||
14. [ ] Add trend analysis tools
|
||||
15. [ ] Set up cache invalidation
|
||||
16. [ ] Add cache warming jobs
|
||||
17. [ ] Research map providers
|
||||
18. [ ] Plan geocoding strategy
|
||||
208
memory-bank/features/AreaOrganization.md
Normal file
208
memory-bank/features/AreaOrganization.md
Normal file
@@ -0,0 +1,208 @@
|
||||
# Area Organization System
|
||||
|
||||
## Overview
|
||||
The Area Organization system provides a flexible way to structure and order areas within a park. It supports both flat and nested hierarchies, with drag-and-drop reordering capabilities and efficient position management.
|
||||
|
||||
## Database Structure
|
||||
|
||||
### Park Areas Table
|
||||
```sql
|
||||
CREATE TABLE park_areas (
|
||||
id bigint unsigned NOT NULL AUTO_INCREMENT,
|
||||
park_id bigint unsigned NOT NULL,
|
||||
parent_id bigint unsigned NULL,
|
||||
name varchar(255) NOT NULL,
|
||||
slug varchar(255) NOT NULL,
|
||||
description text NULL,
|
||||
opening_date date NULL,
|
||||
closing_date date NULL,
|
||||
position integer NOT NULL DEFAULT 0,
|
||||
created_at timestamp NULL,
|
||||
updated_at timestamp NULL,
|
||||
PRIMARY KEY (id),
|
||||
FOREIGN KEY (park_id) REFERENCES parks(id),
|
||||
FOREIGN KEY (parent_id) REFERENCES park_areas(id),
|
||||
INDEX idx_ordering (park_id, position),
|
||||
INDEX idx_hierarchy (park_id, parent_id)
|
||||
);
|
||||
```
|
||||
|
||||
## Key Features
|
||||
|
||||
### 1. Position Management
|
||||
- Automatic position assignment for new areas
|
||||
- Zero-based position indexing
|
||||
- Position maintenance during reordering
|
||||
- Efficient batch updates for position changes
|
||||
|
||||
### 2. Hierarchical Structure
|
||||
- Parent-child relationships between areas
|
||||
- Unlimited nesting depth
|
||||
- Separate position sequences per parent
|
||||
- Cascading deletion options
|
||||
|
||||
### 3. Query Optimization
|
||||
- Compound indexes for efficient ordering
|
||||
- Optimized parent-child lookups
|
||||
- Position-based sorting
|
||||
- Scoped uniqueness constraints
|
||||
|
||||
## Implementation Details
|
||||
|
||||
### Position Management
|
||||
1. New Area Creation
|
||||
```php
|
||||
protected static function boot()
|
||||
{
|
||||
parent::boot();
|
||||
static::creating(function (ParkArea $area) {
|
||||
if (is_null($area->position)) {
|
||||
$area->position = $area->getNextPosition();
|
||||
}
|
||||
});
|
||||
}
|
||||
```
|
||||
|
||||
2. Position Calculation
|
||||
```php
|
||||
public function getNextPosition(): int
|
||||
{
|
||||
$maxPosition = static::where('park_id', $this->park_id)
|
||||
->where('parent_id', $this->parent_id)
|
||||
->max('position');
|
||||
|
||||
return ($maxPosition ?? -1) + 1;
|
||||
}
|
||||
```
|
||||
|
||||
3. Position Updates
|
||||
```php
|
||||
public function moveToPosition(int $newPosition): void
|
||||
{
|
||||
if ($newPosition === $this->position) {
|
||||
return;
|
||||
}
|
||||
|
||||
$oldPosition = $this->position;
|
||||
|
||||
if ($newPosition > $oldPosition) {
|
||||
// Moving down: decrement positions of items in between
|
||||
static::where('park_id', $this->park_id)
|
||||
->where('parent_id', $this->parent_id)
|
||||
->whereBetween('position', [$oldPosition + 1, $newPosition])
|
||||
->decrement('position');
|
||||
} else {
|
||||
// Moving up: increment positions of items in between
|
||||
static::where('park_id', $this->park_id)
|
||||
->where('parent_id', $this->parent_id)
|
||||
->whereBetween('position', [$newPosition, $oldPosition - 1])
|
||||
->increment('position');
|
||||
}
|
||||
|
||||
$this->update(['position' => $newPosition]);
|
||||
}
|
||||
```
|
||||
|
||||
### Hierarchical Relationships
|
||||
1. Parent Relationship
|
||||
```php
|
||||
public function parent(): BelongsTo
|
||||
{
|
||||
return $this->belongsTo(ParkArea::class, 'parent_id');
|
||||
}
|
||||
```
|
||||
|
||||
2. Children Relationship
|
||||
```php
|
||||
public function children(): HasMany
|
||||
{
|
||||
return $this->hasMany(ParkArea::class, 'parent_id')
|
||||
->orderBy('position');
|
||||
}
|
||||
```
|
||||
|
||||
3. Helper Methods
|
||||
```php
|
||||
public function hasChildren(): bool
|
||||
{
|
||||
return $this->children()->exists();
|
||||
}
|
||||
|
||||
public function isTopLevel(): bool
|
||||
{
|
||||
return is_null($this->parent_id);
|
||||
}
|
||||
```
|
||||
|
||||
## Usage Examples
|
||||
|
||||
### Creating a New Area
|
||||
```php
|
||||
$area = new ParkArea([
|
||||
'name' => 'Adventure Zone',
|
||||
'description' => 'Thrilling rides area',
|
||||
]);
|
||||
$park->areas()->save($area);
|
||||
```
|
||||
|
||||
### Moving an Area
|
||||
```php
|
||||
$area->moveToPosition(5);
|
||||
```
|
||||
|
||||
### Adding a Sub-Area
|
||||
```php
|
||||
$subArea = new ParkArea([
|
||||
'name' => 'Coaster Corner',
|
||||
'parent_id' => $area->id,
|
||||
]);
|
||||
$park->areas()->save($subArea);
|
||||
```
|
||||
|
||||
## Future Enhancements
|
||||
1. [ ] Add drag-and-drop reordering UI
|
||||
2. [ ] Implement position validation
|
||||
3. [ ] Add move restrictions
|
||||
4. [ ] Implement area statistics
|
||||
5. [ ] Add bulk reordering
|
||||
6. [ ] Implement depth limits
|
||||
7. [ ] Add position caching
|
||||
8. [ ] Implement move history
|
||||
|
||||
## Security Considerations
|
||||
1. Position Validation
|
||||
- Prevent out-of-bounds positions
|
||||
- Validate parent-child relationships
|
||||
- Check for circular references
|
||||
|
||||
2. Access Control
|
||||
- Restrict reordering permissions
|
||||
- Validate park ownership
|
||||
- Log position changes
|
||||
|
||||
## Performance Optimization
|
||||
1. Batch Updates
|
||||
- Use transactions for moves
|
||||
- Minimize position updates
|
||||
- Cache position values
|
||||
|
||||
2. Query Optimization
|
||||
- Use compound indexes
|
||||
- Minimize nested queries
|
||||
- Efficient position calculations
|
||||
|
||||
## Testing Strategy
|
||||
1. Unit Tests
|
||||
- [ ] Position calculation
|
||||
- [ ] Move operations
|
||||
- [ ] Parent-child relationships
|
||||
|
||||
2. Integration Tests
|
||||
- [ ] Reordering flows
|
||||
- [ ] Nested operations
|
||||
- [ ] Position maintenance
|
||||
|
||||
3. Performance Tests
|
||||
- [ ] Large-scale reordering
|
||||
- [ ] Nested structure queries
|
||||
- [ ] Position update efficiency
|
||||
216
memory-bank/features/AreaStatistics.md
Normal file
216
memory-bank/features/AreaStatistics.md
Normal file
@@ -0,0 +1,216 @@
|
||||
# Area Statistics System
|
||||
|
||||
## Overview
|
||||
The Area Statistics system provides comprehensive tracking and management of various metrics for park areas, including ride counts, visitor statistics, and historical data. This system enables data-driven insights and performance monitoring at both the area and park level.
|
||||
|
||||
## Database Structure
|
||||
|
||||
### Park Areas Table Statistics Fields
|
||||
```sql
|
||||
ALTER TABLE park_areas ADD (
|
||||
-- Ride statistics
|
||||
ride_count integer DEFAULT 0,
|
||||
coaster_count integer DEFAULT 0,
|
||||
flat_ride_count integer DEFAULT 0,
|
||||
water_ride_count integer DEFAULT 0,
|
||||
|
||||
-- Visitor statistics
|
||||
daily_capacity integer NULL,
|
||||
peak_wait_time integer NULL,
|
||||
average_rating decimal(3,2) NULL,
|
||||
|
||||
-- Historical data
|
||||
total_rides_operated integer DEFAULT 0,
|
||||
retired_rides_count integer DEFAULT 0,
|
||||
last_new_ride_added date NULL,
|
||||
|
||||
-- Indexes
|
||||
INDEX idx_rides (park_id, ride_count),
|
||||
INDEX idx_coasters (park_id, coaster_count),
|
||||
INDEX idx_rating (park_id, average_rating)
|
||||
);
|
||||
```
|
||||
|
||||
## Components
|
||||
|
||||
### 1. HasAreaStatistics Trait
|
||||
Located in `app/Traits/HasAreaStatistics.php`
|
||||
|
||||
Purpose:
|
||||
- Provides statistics management functionality
|
||||
- Handles calculations and formatting
|
||||
- Manages data updates
|
||||
- Tracks historical metrics
|
||||
|
||||
Features:
|
||||
1. Ride Statistics
|
||||
- Total ride count
|
||||
- Type distribution
|
||||
- Coaster percentage
|
||||
- Historical tracking
|
||||
|
||||
2. Visitor Metrics
|
||||
- Daily capacity
|
||||
- Peak wait times
|
||||
- Average ratings
|
||||
- Formatted displays
|
||||
|
||||
3. Historical Data
|
||||
- Total rides operated
|
||||
- Retirement tracking
|
||||
- Last addition date
|
||||
- Retirement rate
|
||||
|
||||
## Implementation Details
|
||||
|
||||
### Ride Count Management
|
||||
```php
|
||||
public function updateRideCounts(array $counts): void
|
||||
{
|
||||
$this->update([
|
||||
'ride_count' => $counts['total'] ?? 0,
|
||||
'coaster_count' => $counts['coasters'] ?? 0,
|
||||
'flat_ride_count' => $counts['flat_rides'] ?? 0,
|
||||
'water_ride_count' => $counts['water_rides'] ?? 0,
|
||||
]);
|
||||
}
|
||||
```
|
||||
|
||||
### Visitor Statistics
|
||||
```php
|
||||
public function updateVisitorStats(
|
||||
int $dailyCapacity,
|
||||
int $peakWaitTime,
|
||||
float $rating
|
||||
): void
|
||||
{
|
||||
$this->update([
|
||||
'daily_capacity' => $dailyCapacity,
|
||||
'peak_wait_time' => $peakWaitTime,
|
||||
'average_rating' => round($rating, 2),
|
||||
]);
|
||||
}
|
||||
```
|
||||
|
||||
### Historical Tracking
|
||||
```php
|
||||
public function recordNewRide(): void
|
||||
{
|
||||
$this->increment('total_rides_operated');
|
||||
$this->update(['last_new_ride_added' => now()]);
|
||||
}
|
||||
|
||||
public function recordRetirement(): void
|
||||
{
|
||||
$this->increment('retired_rides_count');
|
||||
}
|
||||
```
|
||||
|
||||
## Display Features
|
||||
|
||||
### 1. Rating Display
|
||||
- Star-based visualization (★★★☆☆)
|
||||
- Numerical rating with one decimal
|
||||
- "Not rated" fallback
|
||||
|
||||
### 2. Capacity Display
|
||||
- Formatted numbers with commas
|
||||
- "riders/day" unit
|
||||
- Unknown capacity handling
|
||||
|
||||
### 3. Wait Time Display
|
||||
- Minutes format
|
||||
- Peak time indication
|
||||
- Unknown time handling
|
||||
|
||||
## Data Analysis
|
||||
|
||||
### 1. Distribution Analysis
|
||||
```php
|
||||
public function getRideDistributionAttribute(): array
|
||||
{
|
||||
return [
|
||||
'coasters' => $this->coaster_count ?? 0,
|
||||
'flat_rides' => $this->flat_ride_count ?? 0,
|
||||
'water_rides' => $this->water_ride_count ?? 0,
|
||||
];
|
||||
}
|
||||
```
|
||||
|
||||
### 2. Historical Analysis
|
||||
```php
|
||||
public function getHistoricalStatsAttribute(): array
|
||||
{
|
||||
return [
|
||||
'total_operated' => $this->total_rides_operated,
|
||||
'retired_count' => $this->retired_rides_count,
|
||||
'last_addition' => $this->last_new_ride_added?->format('M Y'),
|
||||
'retirement_rate' => $this->getRetirementRate(),
|
||||
];
|
||||
}
|
||||
```
|
||||
|
||||
## Performance Optimization
|
||||
|
||||
### 1. Database Indexes
|
||||
- Compound indexes for common queries
|
||||
- Efficient sorting support
|
||||
- Quick statistical lookups
|
||||
|
||||
### 2. Caching Strategy
|
||||
- [ ] Implement statistics caching
|
||||
- [ ] Add cache invalidation rules
|
||||
- [ ] Set up cache warming
|
||||
|
||||
## Future Enhancements
|
||||
1. [ ] Add seasonal statistics
|
||||
2. [ ] Implement trend analysis
|
||||
3. [ ] Add capacity forecasting
|
||||
4. [ ] Create statistical reports
|
||||
5. [ ] Add comparison tools
|
||||
6. [ ] Implement benchmarking
|
||||
7. [ ] Add historical graphs
|
||||
8. [ ] Create export functionality
|
||||
|
||||
## Integration Points
|
||||
1. Park Model
|
||||
- Area statistics rollup
|
||||
- Park-wide metrics
|
||||
- Comparative analysis
|
||||
|
||||
2. Rides System
|
||||
- Automatic count updates
|
||||
- Type classification
|
||||
- Capacity calculation
|
||||
|
||||
3. Visitor System
|
||||
- Wait time tracking
|
||||
- Rating collection
|
||||
- Capacity monitoring
|
||||
|
||||
## Security Considerations
|
||||
1. Data Validation
|
||||
- Range checks
|
||||
- Type validation
|
||||
- Update authorization
|
||||
|
||||
2. Access Control
|
||||
- Statistics visibility
|
||||
- Update permissions
|
||||
- Export restrictions
|
||||
|
||||
## Testing Strategy
|
||||
1. Unit Tests
|
||||
- [ ] Calculation accuracy
|
||||
- [ ] Format handling
|
||||
- [ ] Edge cases
|
||||
|
||||
2. Integration Tests
|
||||
- [ ] Update operations
|
||||
- [ ] Rollup functionality
|
||||
- [ ] Cache invalidation
|
||||
|
||||
3. Performance Tests
|
||||
- [ ] Large dataset handling
|
||||
- [ ] Update efficiency
|
||||
- [ ] Query optimization
|
||||
238
memory-bank/features/LocationSystem.md
Normal file
238
memory-bank/features/LocationSystem.md
Normal file
@@ -0,0 +1,238 @@
|
||||
# Location System
|
||||
|
||||
## Overview
|
||||
The Location System provides comprehensive location management for parks, areas, and other entities through polymorphic relationships. It includes geocoding, map integration, and location-based search capabilities.
|
||||
|
||||
## Components
|
||||
|
||||
### 1. Database Structure
|
||||
|
||||
#### Locations Table
|
||||
```sql
|
||||
CREATE TABLE locations (
|
||||
id bigint PRIMARY KEY,
|
||||
locatable_type varchar(255),
|
||||
locatable_id bigint,
|
||||
address varchar(255) NULL,
|
||||
city varchar(255),
|
||||
state varchar(255) NULL,
|
||||
country varchar(255),
|
||||
postal_code varchar(255) NULL,
|
||||
latitude decimal(10,8),
|
||||
longitude decimal(11,8),
|
||||
elevation decimal(8,2) NULL,
|
||||
timezone varchar(255) NULL,
|
||||
metadata json NULL,
|
||||
is_approximate boolean DEFAULT false,
|
||||
source varchar(255) NULL,
|
||||
geocoding_data json NULL,
|
||||
geocoded_at timestamp NULL,
|
||||
created_at timestamp,
|
||||
updated_at timestamp,
|
||||
|
||||
INDEX idx_coordinates (latitude, longitude),
|
||||
INDEX idx_location (country, state, city),
|
||||
INDEX idx_postal (postal_code)
|
||||
);
|
||||
```
|
||||
|
||||
### 2. Models
|
||||
|
||||
#### Location Model
|
||||
- Polymorphic relationships
|
||||
- Geocoding integration
|
||||
- Coordinate handling
|
||||
- Distance calculations
|
||||
|
||||
#### HasLocation Trait
|
||||
- Location relationship
|
||||
- Coordinate accessors
|
||||
- Distance methods
|
||||
- Map integration
|
||||
|
||||
### 3. Services
|
||||
|
||||
#### GeocodeService
|
||||
- Address lookup
|
||||
- Coordinate validation
|
||||
- Batch processing
|
||||
- Cache management
|
||||
|
||||
#### LocationSearchService
|
||||
- Distance-based search
|
||||
- Boundary queries
|
||||
- Clustering support
|
||||
- Performance optimization
|
||||
|
||||
### 4. Components
|
||||
|
||||
#### LocationSelector
|
||||
- Map integration
|
||||
- Address search
|
||||
- Coordinate picker
|
||||
- Validation feedback
|
||||
|
||||
#### LocationDisplay
|
||||
- Map rendering
|
||||
- Marker clustering
|
||||
- Info windows
|
||||
- Interactive controls
|
||||
|
||||
## Implementation Details
|
||||
|
||||
### 1. Model Structure
|
||||
```php
|
||||
class Location extends Model
|
||||
{
|
||||
protected $fillable = [
|
||||
'address',
|
||||
'city',
|
||||
'state',
|
||||
'country',
|
||||
'postal_code',
|
||||
'latitude',
|
||||
'longitude',
|
||||
'elevation',
|
||||
'timezone',
|
||||
'metadata',
|
||||
'is_approximate',
|
||||
'source',
|
||||
'geocoding_data',
|
||||
'geocoded_at',
|
||||
];
|
||||
|
||||
protected $casts = [
|
||||
'latitude' => 'decimal:8',
|
||||
'longitude' => 'decimal:8',
|
||||
'elevation' => 'decimal:2',
|
||||
'metadata' => 'array',
|
||||
'geocoding_data' => 'array',
|
||||
'geocoded_at' => 'datetime',
|
||||
'is_approximate' => 'boolean',
|
||||
];
|
||||
}
|
||||
```
|
||||
|
||||
### 2. Trait Implementation
|
||||
```php
|
||||
trait HasLocation
|
||||
{
|
||||
public function location()
|
||||
{
|
||||
return $this->morphOne(Location::class, 'locatable');
|
||||
}
|
||||
|
||||
public function getCoordinatesAttribute()
|
||||
{
|
||||
return [
|
||||
'lat' => $this->location?->latitude,
|
||||
'lng' => $this->location?->longitude,
|
||||
];
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Integration Points
|
||||
|
||||
### 1. Parks System
|
||||
- Location assignment
|
||||
- Map display
|
||||
- Area boundaries
|
||||
- Distance calculations
|
||||
|
||||
### 2. Search System
|
||||
- Location-based filtering
|
||||
- Distance sorting
|
||||
- Boundary queries
|
||||
- Clustering support
|
||||
|
||||
### 3. API Integration
|
||||
- Geocoding services
|
||||
- Map providers
|
||||
- Data validation
|
||||
- Error handling
|
||||
|
||||
## Performance Considerations
|
||||
|
||||
### 1. Database Design
|
||||
- Efficient indexes
|
||||
- Coordinate precision
|
||||
- Query optimization
|
||||
- Cache strategy
|
||||
|
||||
### 2. Geocoding
|
||||
- Request limiting
|
||||
- Cache management
|
||||
- Batch processing
|
||||
- Error handling
|
||||
|
||||
### 3. Map Integration
|
||||
- Lazy loading
|
||||
- Marker clustering
|
||||
- Viewport management
|
||||
- Memory optimization
|
||||
|
||||
## Future Enhancements
|
||||
|
||||
1. [ ] Add route planning
|
||||
2. [ ] Implement geofencing
|
||||
3. [ ] Add location sharing
|
||||
4. [ ] Create heatmaps
|
||||
5. [ ] Add offline support
|
||||
6. [ ] Implement navigation
|
||||
7. [ ] Add location history
|
||||
8. [ ] Create location alerts
|
||||
|
||||
## Security Considerations
|
||||
|
||||
### 1. Data Protection
|
||||
- Coordinate validation
|
||||
- Input sanitization
|
||||
- Access control
|
||||
- Audit logging
|
||||
|
||||
### 2. API Security
|
||||
- Rate limiting
|
||||
- Token management
|
||||
- Error handling
|
||||
- Request validation
|
||||
|
||||
## Testing Strategy
|
||||
|
||||
### 1. Unit Tests
|
||||
- [ ] Coordinate validation
|
||||
- [ ] Distance calculations
|
||||
- [ ] Geocoding integration
|
||||
- [ ] Model relationships
|
||||
|
||||
### 2. Integration Tests
|
||||
- [ ] Map integration
|
||||
- [ ] Search functionality
|
||||
- [ ] API communication
|
||||
- [ ] Cache management
|
||||
|
||||
### 3. Performance Tests
|
||||
- [ ] Large datasets
|
||||
- [ ] Clustering efficiency
|
||||
- [ ] Query optimization
|
||||
- [ ] Memory usage
|
||||
|
||||
## Monitoring
|
||||
|
||||
### 1. Performance Metrics
|
||||
- [ ] Query timing
|
||||
- [ ] API response times
|
||||
- [ ] Cache hit rates
|
||||
- [ ] Memory usage
|
||||
|
||||
### 2. Error Tracking
|
||||
- [ ] Geocoding failures
|
||||
- [ ] API errors
|
||||
- [ ] Invalid coordinates
|
||||
- [ ] Cache misses
|
||||
|
||||
### 3. Usage Analytics
|
||||
- [ ] Search patterns
|
||||
- [ ] Popular locations
|
||||
- [ ] API usage
|
||||
- [ ] User interactions
|
||||
261
memory-bank/features/ParksManagement.md
Normal file
261
memory-bank/features/ParksManagement.md
Normal file
@@ -0,0 +1,261 @@
|
||||
# Parks Management System
|
||||
|
||||
## Overview
|
||||
The Parks Management system provides a comprehensive interface for creating, reading, updating, and deleting theme parks and their areas. It implements a responsive, user-friendly interface while maintaining data integrity and proper relationships.
|
||||
|
||||
## Components
|
||||
|
||||
### 1. ParkFormComponent
|
||||
Located in `app/Livewire/ParkFormComponent.php`
|
||||
|
||||
Purpose:
|
||||
- Handles both creation and editing of parks
|
||||
- Manages form state and validation
|
||||
- Handles relationships with operators
|
||||
- Updates statistics automatically
|
||||
|
||||
Features:
|
||||
- Responsive form layout
|
||||
- Real-time validation
|
||||
- Status management with enum
|
||||
- Operator selection
|
||||
- Date range validation
|
||||
- Automatic statistics updates
|
||||
|
||||
Form Sections:
|
||||
1. Basic Information
|
||||
- Park name
|
||||
- Operator selection
|
||||
- Description
|
||||
2. Status and Dates
|
||||
- Operating status
|
||||
- Opening/closing dates
|
||||
3. Additional Details
|
||||
- Operating season
|
||||
- Size in acres
|
||||
- Website
|
||||
|
||||
### 2. ParkListComponent
|
||||
Located in `app/Livewire/ParkListComponent.php`
|
||||
|
||||
Purpose:
|
||||
- Displays paginated list of parks
|
||||
- Provides filtering and sorting capabilities
|
||||
- Handles search functionality
|
||||
- Manages park status display
|
||||
|
||||
Features:
|
||||
1. Search and Filtering
|
||||
- Text search across name and description
|
||||
- Status filtering using ParkStatus enum
|
||||
- Operator filtering
|
||||
- Multiple sort options
|
||||
|
||||
2. Sorting Options
|
||||
- Name (default)
|
||||
- Opening Date
|
||||
- Ride Count
|
||||
- Coaster Count
|
||||
- Size
|
||||
|
||||
3. Display Features
|
||||
- Responsive grid layout
|
||||
- Status badges with colors
|
||||
- Key statistics display
|
||||
- Quick access to edit/view
|
||||
- Website links
|
||||
- Operator information
|
||||
|
||||
### 3. ParkAreaFormComponent
|
||||
Located in `app/Livewire/ParkAreaFormComponent.php`
|
||||
|
||||
Purpose:
|
||||
- Manages creation and editing of park areas
|
||||
- Handles area-specific validation
|
||||
- Maintains park context
|
||||
- Manages opening/closing dates
|
||||
|
||||
Features:
|
||||
1. Form Organization
|
||||
- Area basic information section
|
||||
- Dates management section
|
||||
- Park context display
|
||||
- Validation feedback
|
||||
|
||||
2. Validation Rules
|
||||
- Name uniqueness within park
|
||||
- Date range validation
|
||||
- Required fields handling
|
||||
- Custom error messages
|
||||
|
||||
3. Data Management
|
||||
- Park-scoped slugs
|
||||
- Automatic slug generation
|
||||
- History tracking
|
||||
- Date formatting
|
||||
|
||||
### 4. ParkAreaListComponent
|
||||
Located in `app/Livewire/ParkAreaListComponent.php`
|
||||
|
||||
Purpose:
|
||||
- Displays and manages areas within a park
|
||||
- Provides search and filtering
|
||||
- Handles area deletion
|
||||
- Shows operating status
|
||||
|
||||
Features:
|
||||
1. List Management
|
||||
- Paginated area display
|
||||
- Search functionality
|
||||
- Sort by name or date
|
||||
- Show/hide closed areas
|
||||
|
||||
2. Area Display
|
||||
- Area name and description
|
||||
- Opening/closing dates
|
||||
- Operating status
|
||||
- Quick actions
|
||||
|
||||
3. Actions
|
||||
- Edit area
|
||||
- Delete area with confirmation
|
||||
- Add new area
|
||||
- View area details
|
||||
|
||||
4. Filtering Options
|
||||
- Text search
|
||||
- Operating status filter
|
||||
- Sort direction toggle
|
||||
- Date-based sorting
|
||||
|
||||
## UI/UX Design Decisions
|
||||
|
||||
### Form Design
|
||||
1. Sectioned Layout
|
||||
- Groups related fields together
|
||||
- Improves visual hierarchy
|
||||
- Makes long form more manageable
|
||||
|
||||
2. Responsive Grid
|
||||
- Single column on mobile
|
||||
- Multi-column on larger screens
|
||||
- Maintains readability at all sizes
|
||||
|
||||
3. Validation Feedback
|
||||
- Immediate error messages
|
||||
- Clear error states
|
||||
- Success notifications
|
||||
|
||||
### List Design
|
||||
1. Card Layout
|
||||
- Visual separation of items
|
||||
- Key information at a glance
|
||||
- Status prominence
|
||||
- Action buttons
|
||||
|
||||
2. Filter Controls
|
||||
- Prominent search
|
||||
- Quick status filtering
|
||||
- Flexible sorting
|
||||
- Toggle controls
|
||||
|
||||
## Data Handling
|
||||
|
||||
### Validation Rules
|
||||
```php
|
||||
// Park Rules
|
||||
[
|
||||
'name' => ['required', 'string', 'min:2', 'max:255', 'unique'],
|
||||
'description' => ['nullable', 'string'],
|
||||
'status' => ['required', 'enum'],
|
||||
'opening_date' => ['nullable', 'date'],
|
||||
'closing_date' => ['nullable', 'date', 'after:opening_date'],
|
||||
'operating_season' => ['nullable', 'string', 'max:255'],
|
||||
'size_acres' => ['nullable', 'numeric', 'min:0', 'max:999999.99'],
|
||||
'website' => ['nullable', 'url', 'max:255'],
|
||||
'operator_id' => ['nullable', 'exists:operators,id'],
|
||||
]
|
||||
|
||||
// Area Rules
|
||||
[
|
||||
'name' => ['required', 'string', 'min:2', 'max:255', 'unique:within_park'],
|
||||
'description' => ['nullable', 'string'],
|
||||
'opening_date' => ['nullable', 'date'],
|
||||
'closing_date' => ['nullable', 'date', 'after:opening_date'],
|
||||
]
|
||||
```
|
||||
|
||||
### Query Optimization
|
||||
1. Eager Loading
|
||||
- Operator relationship
|
||||
- Areas relationship
|
||||
- Future: Rides relationship
|
||||
|
||||
2. Search Implementation
|
||||
- Combined name and description search
|
||||
- Case-insensitive matching
|
||||
- Proper index usage
|
||||
|
||||
3. Filter Efficiency
|
||||
- Status index
|
||||
- Operator foreign key index
|
||||
- Compound sorting
|
||||
|
||||
## Future Enhancements
|
||||
1. [ ] Add image upload support
|
||||
2. [ ] Implement location selection
|
||||
3. [ ] Add preview functionality
|
||||
4. [ ] Add duplicate detection
|
||||
5. [ ] Implement draft saving
|
||||
6. [ ] Add bulk operations
|
||||
7. [ ] Add import/export functionality
|
||||
8. [ ] Add map view option
|
||||
9. [ ] Implement advanced search
|
||||
10. [ ] Add comparison feature
|
||||
11. [ ] Add area reordering
|
||||
12. [ ] Implement area statistics
|
||||
13. [ ] Add drag-and-drop sorting
|
||||
14. [ ] Implement nested areas
|
||||
|
||||
## Integration Points
|
||||
1. Operators
|
||||
- Selection in form
|
||||
- Statistics updates
|
||||
- Relationship maintenance
|
||||
|
||||
2. Slug History
|
||||
- Automatic slug generation
|
||||
- Historical slug tracking
|
||||
- SEO-friendly URLs
|
||||
|
||||
3. Park Areas
|
||||
- Nested management
|
||||
- Area organization
|
||||
- Statistics rollup
|
||||
|
||||
## Security Considerations
|
||||
1. Authorization
|
||||
- [ ] Implement role-based access
|
||||
- [ ] Add ownership checks
|
||||
- [ ] Audit logging
|
||||
|
||||
2. Validation
|
||||
- Input sanitization
|
||||
- CSRF protection
|
||||
- Rate limiting
|
||||
|
||||
## Testing Strategy
|
||||
1. Unit Tests
|
||||
- [ ] Validation rules
|
||||
- [ ] Status transitions
|
||||
- [ ] Statistics updates
|
||||
|
||||
2. Integration Tests
|
||||
- [ ] Form submission
|
||||
- [ ] Relationship updates
|
||||
- [ ] Slug generation
|
||||
|
||||
3. Feature Tests
|
||||
- [ ] Complete CRUD flow
|
||||
- [ ] Authorization rules
|
||||
- [ ] Edge cases
|
||||
100
memory-bank/features/SlugHistorySystem.md
Normal file
100
memory-bank/features/SlugHistorySystem.md
Normal file
@@ -0,0 +1,100 @@
|
||||
# Slug History System
|
||||
|
||||
## Overview
|
||||
The slug history system provides a way to track changes to model slugs over time, ensuring that old URLs continue to work even after slugs are updated. This is particularly important for maintaining SEO value and preventing broken links.
|
||||
|
||||
## Components
|
||||
|
||||
### 1. HasSlugHistory Trait
|
||||
Located in `app/Traits/HasSlugHistory.php`
|
||||
|
||||
Key Features:
|
||||
- Automatic slug generation from name field
|
||||
- Tracking of slug changes
|
||||
- Historical slug lookup
|
||||
- Handling of duplicate slugs
|
||||
- Polymorphic relationship with SlugHistory model
|
||||
|
||||
### 2. SlugHistory Model
|
||||
Located in `app/Models/SlugHistory.php`
|
||||
|
||||
Purpose:
|
||||
- Stores historical slugs for any model using HasSlugHistory trait
|
||||
- Uses polymorphic relationships to link with parent models
|
||||
- Maintains timestamps for tracking when slugs were used
|
||||
|
||||
## Database Structure
|
||||
|
||||
```sql
|
||||
CREATE TABLE slug_histories (
|
||||
id bigint unsigned NOT NULL AUTO_INCREMENT,
|
||||
sluggable_type varchar(255) NOT NULL,
|
||||
sluggable_id bigint unsigned NOT NULL,
|
||||
slug varchar(255) NOT NULL,
|
||||
created_at timestamp NULL DEFAULT NULL,
|
||||
updated_at timestamp NULL DEFAULT NULL,
|
||||
PRIMARY KEY (id),
|
||||
KEY idx_sluggable (sluggable_type, slug)
|
||||
);
|
||||
```
|
||||
|
||||
## Usage Example
|
||||
|
||||
```php
|
||||
class Operator extends Model
|
||||
{
|
||||
use HasSlugHistory;
|
||||
|
||||
// Model implementation
|
||||
}
|
||||
|
||||
// Finding by current or historical slug
|
||||
$operator = Operator::findBySlug('old-slug');
|
||||
$operator = Operator::findBySlugOrFail('old-slug');
|
||||
```
|
||||
|
||||
## Current Implementation
|
||||
|
||||
Models using the system:
|
||||
- Operator (park operators)
|
||||
- Manufacturer (ride manufacturers)
|
||||
- Park (to be implemented)
|
||||
- ParkArea (to be implemented)
|
||||
|
||||
## Features
|
||||
1. Automatic Slug Generation
|
||||
- Converts name to URL-friendly format
|
||||
- Handles duplicates by appending numbers
|
||||
- Triggered on model creation
|
||||
|
||||
2. History Tracking
|
||||
- Saves old slugs when updated
|
||||
- Maintains chronological order
|
||||
- Links to original model via polymorphic relationship
|
||||
|
||||
3. Slug Lookup
|
||||
- Checks current slugs first
|
||||
- Falls back to historical slugs
|
||||
- Maintains efficient indexes for quick lookups
|
||||
|
||||
## Benefits
|
||||
1. SEO Friendly
|
||||
- Maintains link equity
|
||||
- Prevents 404 errors
|
||||
- Supports URL structure changes
|
||||
|
||||
2. User Experience
|
||||
- Old bookmarks continue to work
|
||||
- Prevents broken links
|
||||
- Transparent to end users
|
||||
|
||||
3. Performance
|
||||
- Efficient database indexing
|
||||
- Minimal overhead
|
||||
- Cached lookups (to be implemented)
|
||||
|
||||
## Future Enhancements
|
||||
1. [ ] Add caching layer for frequent lookups
|
||||
2. [ ] Implement automatic redirects with proper status codes
|
||||
3. [ ] Add slug cleanup for old, unused slugs
|
||||
4. [ ] Add analytics for tracking slug usage
|
||||
230
memory-bank/features/StatisticsCaching.md
Normal file
230
memory-bank/features/StatisticsCaching.md
Normal file
@@ -0,0 +1,230 @@
|
||||
# Statistics Caching System
|
||||
|
||||
## Overview
|
||||
The Statistics Caching system provides efficient caching and retrieval of statistics across all levels of the theme park hierarchy. It implements a robust caching strategy with automatic invalidation, cache warming, and performance monitoring.
|
||||
|
||||
## Components
|
||||
|
||||
### 1. Cache Structure
|
||||
|
||||
#### Key Prefixes
|
||||
```php
|
||||
protected const AREA_PREFIX = 'stats:area:';
|
||||
protected const PARK_PREFIX = 'stats:park:';
|
||||
protected const OPERATOR_PREFIX = 'stats:operator:';
|
||||
```
|
||||
|
||||
#### Cache TTL
|
||||
```php
|
||||
protected const CACHE_TTL = 86400; // 24 hours
|
||||
```
|
||||
|
||||
### 2. StatisticsCacheService
|
||||
Located in `app/Services/StatisticsCacheService.php`
|
||||
|
||||
Purpose:
|
||||
- Manage statistics caching
|
||||
- Handle cache invalidation
|
||||
- Provide cache warming
|
||||
- Monitor cache performance
|
||||
|
||||
Features:
|
||||
1. Caching Operations
|
||||
- Area statistics
|
||||
- Park rollups
|
||||
- Operator aggregates
|
||||
- Batch processing
|
||||
|
||||
2. Cache Management
|
||||
- Automatic invalidation
|
||||
- Selective updates
|
||||
- Cache warming
|
||||
- Error handling
|
||||
|
||||
## Implementation Details
|
||||
|
||||
### Area Statistics Cache
|
||||
```php
|
||||
[
|
||||
'ride_distribution' => [
|
||||
'coasters' => 5,
|
||||
'flat_rides' => 12,
|
||||
'water_rides' => 3,
|
||||
],
|
||||
'daily_capacity' => '25,000 riders/day',
|
||||
'rating' => '★★★★☆ (4.2)',
|
||||
'wait_time' => '45 minutes',
|
||||
'historical' => [
|
||||
'total_operated' => 25,
|
||||
'retired_count' => 5,
|
||||
'last_addition' => 'Mar 2024',
|
||||
],
|
||||
'updated_at' => '2024-02-23 19:30:00',
|
||||
]
|
||||
```
|
||||
|
||||
### Park Statistics Cache
|
||||
```php
|
||||
[
|
||||
'area_distribution' => [
|
||||
'total' => 8,
|
||||
'operating' => 7,
|
||||
'closed' => 1,
|
||||
],
|
||||
'ride_distribution' => [
|
||||
'coasters' => 12,
|
||||
'flat_rides' => 35,
|
||||
'water_rides' => 8,
|
||||
],
|
||||
'daily_capacity' => '75,000 riders/day',
|
||||
'rating' => '★★★★★ (4.8)',
|
||||
'wait_time' => '35 minutes',
|
||||
'historical' => [...],
|
||||
'performance' => [
|
||||
'utilization' => '85%',
|
||||
'peak_attendance' => '65,000',
|
||||
'satisfaction' => '4.5/5.0',
|
||||
],
|
||||
'updated_at' => '2024-02-23 19:30:00',
|
||||
]
|
||||
```
|
||||
|
||||
### Operator Statistics Cache
|
||||
```php
|
||||
[
|
||||
'park_count' => 5,
|
||||
'operating_parks' => 4,
|
||||
'closed_parks' => 1,
|
||||
'total_rides' => 275,
|
||||
'total_coasters' => 45,
|
||||
'average_rating' => 4.6,
|
||||
'total_capacity' => 350000,
|
||||
'updated_at' => '2024-02-23 19:30:00',
|
||||
]
|
||||
```
|
||||
|
||||
## Cache Management
|
||||
|
||||
### 1. Invalidation Strategy
|
||||
- Automatic invalidation on updates
|
||||
- Cascading invalidation
|
||||
- Selective cache clearing
|
||||
- Error handling
|
||||
|
||||
### 2. Cache Warming
|
||||
```php
|
||||
public function warmCaches(): void
|
||||
{
|
||||
// Process areas in chunks
|
||||
ParkArea::chunk(100, function ($areas) {
|
||||
foreach ($areas as $area) {
|
||||
$this->cacheAreaStatistics($area);
|
||||
}
|
||||
});
|
||||
|
||||
// Process parks in chunks
|
||||
Park::chunk(100, function ($parks) {...});
|
||||
|
||||
// Process operators in chunks
|
||||
Operator::chunk(100, function ($operators) {...});
|
||||
}
|
||||
```
|
||||
|
||||
### 3. Error Handling
|
||||
```php
|
||||
try {
|
||||
Cache::put($key, $data, static::CACHE_TTL);
|
||||
Log::info("Cached statistics for {$type} {$id}");
|
||||
} catch (\Exception $e) {
|
||||
Log::error("Failed to cache statistics: {$e->getMessage()}");
|
||||
}
|
||||
```
|
||||
|
||||
## Performance Optimization
|
||||
|
||||
### 1. Cache Design
|
||||
- Efficient key structure
|
||||
- Optimized data format
|
||||
- Minimal cache churn
|
||||
- Batch operations
|
||||
|
||||
### 2. Memory Usage
|
||||
- Compact data storage
|
||||
- Selective caching
|
||||
- TTL management
|
||||
- Cache size monitoring
|
||||
|
||||
### 3. Invalidation Rules
|
||||
- Smart invalidation
|
||||
- Dependency tracking
|
||||
- Cascade control
|
||||
- Version management
|
||||
|
||||
## Future Enhancements
|
||||
1. [ ] Add Redis support
|
||||
2. [ ] Implement cache tags
|
||||
3. [ ] Add cache versioning
|
||||
4. [ ] Create cache analytics
|
||||
5. [ ] Add cache preloading
|
||||
6. [ ] Implement cache pruning
|
||||
7. [ ] Add cache monitoring
|
||||
8. [ ] Create cache dashboard
|
||||
|
||||
## Integration Points
|
||||
1. Statistics System
|
||||
- Data aggregation
|
||||
- Cache updates
|
||||
- Performance metrics
|
||||
|
||||
2. Event System
|
||||
- Cache invalidation
|
||||
- Update triggers
|
||||
- Error handling
|
||||
|
||||
3. Monitoring System
|
||||
- Cache hit rates
|
||||
- Performance tracking
|
||||
- Error logging
|
||||
|
||||
## Security Considerations
|
||||
1. Data Protection
|
||||
- Cache encryption
|
||||
- Access control
|
||||
- Data validation
|
||||
|
||||
2. Error Handling
|
||||
- Graceful degradation
|
||||
- Fallback mechanisms
|
||||
- Error logging
|
||||
|
||||
## Testing Strategy
|
||||
1. Unit Tests
|
||||
- [ ] Cache operations
|
||||
- [ ] Invalidation rules
|
||||
- [ ] Error handling
|
||||
|
||||
2. Integration Tests
|
||||
- [ ] Cache warming
|
||||
- [ ] Update propagation
|
||||
- [ ] Performance tests
|
||||
|
||||
3. Load Tests
|
||||
- [ ] Cache hit rates
|
||||
- [ ] Memory usage
|
||||
- [ ] Concurrent access
|
||||
|
||||
## Monitoring
|
||||
1. Performance Metrics
|
||||
- [ ] Cache hit rates
|
||||
- [ ] Response times
|
||||
- [ ] Memory usage
|
||||
|
||||
2. Error Tracking
|
||||
- [ ] Failed operations
|
||||
- [ ] Invalid data
|
||||
- [ ] System alerts
|
||||
|
||||
3. Usage Analytics
|
||||
- [ ] Access patterns
|
||||
- [ ] Data freshness
|
||||
- [ ] Cache efficiency
|
||||
226
memory-bank/features/StatisticsRollup.md
Normal file
226
memory-bank/features/StatisticsRollup.md
Normal file
@@ -0,0 +1,226 @@
|
||||
# Statistics Rollup System
|
||||
|
||||
## Overview
|
||||
The Statistics Rollup system provides comprehensive tracking and aggregation of statistics across different levels of the theme park hierarchy: areas, parks, and operators. It ensures data consistency and provides real-time insights through automatic updates and scheduled refreshes.
|
||||
|
||||
## Components
|
||||
|
||||
### 1. Database Structure
|
||||
|
||||
#### Park Areas Table Statistics
|
||||
```sql
|
||||
ALTER TABLE park_areas ADD (
|
||||
ride_count integer DEFAULT 0,
|
||||
coaster_count integer DEFAULT 0,
|
||||
flat_ride_count integer DEFAULT 0,
|
||||
water_ride_count integer DEFAULT 0,
|
||||
daily_capacity integer NULL,
|
||||
peak_wait_time integer NULL,
|
||||
average_rating decimal(3,2) NULL,
|
||||
total_rides_operated integer DEFAULT 0,
|
||||
retired_rides_count integer DEFAULT 0,
|
||||
last_new_ride_added date NULL
|
||||
);
|
||||
```
|
||||
|
||||
#### Parks Table Statistics
|
||||
```sql
|
||||
ALTER TABLE parks ADD (
|
||||
total_areas integer DEFAULT 0,
|
||||
operating_areas integer DEFAULT 0,
|
||||
closed_areas integer DEFAULT 0,
|
||||
total_rides integer DEFAULT 0,
|
||||
total_coasters integer DEFAULT 0,
|
||||
total_flat_rides integer DEFAULT 0,
|
||||
total_water_rides integer DEFAULT 0,
|
||||
total_daily_capacity integer DEFAULT 0,
|
||||
average_wait_time integer NULL,
|
||||
average_rating decimal(3,2) NULL,
|
||||
total_rides_operated integer DEFAULT 0,
|
||||
total_rides_retired integer DEFAULT 0,
|
||||
last_expansion_date date NULL,
|
||||
last_major_update date NULL,
|
||||
utilization_rate decimal(5,2) NULL,
|
||||
peak_daily_attendance integer NULL,
|
||||
guest_satisfaction decimal(3,2) NULL
|
||||
);
|
||||
```
|
||||
|
||||
### 2. Traits
|
||||
|
||||
#### HasAreaStatistics
|
||||
Located in `app/Traits/HasAreaStatistics.php`
|
||||
- Ride count management
|
||||
- Visitor statistics
|
||||
- Historical tracking
|
||||
- Formatted displays
|
||||
|
||||
#### HasParkStatistics
|
||||
Located in `app/Traits/HasParkStatistics.php`
|
||||
- Area statistics rollup
|
||||
- Ride statistics aggregation
|
||||
- Performance metrics
|
||||
- Historical data tracking
|
||||
|
||||
### 3. StatisticsRollupService
|
||||
Located in `app/Services/StatisticsRollupService.php`
|
||||
|
||||
Purpose:
|
||||
- Coordinate statistics updates
|
||||
- Maintain data consistency
|
||||
- Handle events
|
||||
- Schedule refreshes
|
||||
|
||||
Features:
|
||||
1. Hierarchical Updates
|
||||
- Bottom-up propagation
|
||||
- Transaction safety
|
||||
- Batch processing
|
||||
- Event handling
|
||||
|
||||
2. Update Types
|
||||
- Area statistics
|
||||
- Park rollups
|
||||
- Operator aggregates
|
||||
- System-wide refresh
|
||||
|
||||
## Implementation Details
|
||||
|
||||
### Update Flow
|
||||
1. Area Update
|
||||
```php
|
||||
public function updateAreaStatistics(ParkArea $area): void
|
||||
{
|
||||
DB::transaction(function () use ($area) {
|
||||
$this->updateParkStatistics($area->park);
|
||||
});
|
||||
}
|
||||
```
|
||||
|
||||
2. Park Rollup
|
||||
```php
|
||||
public function updateParkStatistics(Park $park): void
|
||||
{
|
||||
DB::transaction(function () use ($park) {
|
||||
$park->updateAreaCounts();
|
||||
$park->updateRideStatistics();
|
||||
$park->updateVisitorStats();
|
||||
// Update operator if exists
|
||||
});
|
||||
}
|
||||
```
|
||||
|
||||
3. Operator Aggregation
|
||||
```php
|
||||
public function updateOperatorStatistics(Operator $operator): void
|
||||
{
|
||||
DB::transaction(function () use ($operator) {
|
||||
// Update park counts
|
||||
// Update ride totals
|
||||
// Update performance metrics
|
||||
});
|
||||
}
|
||||
```
|
||||
|
||||
## Event Handling
|
||||
|
||||
### 1. Ride Events
|
||||
- Addition tracking
|
||||
- Retirement processing
|
||||
- Statistics updates
|
||||
|
||||
### 2. Park Events
|
||||
- Expansion recording
|
||||
- Major updates
|
||||
- Performance tracking
|
||||
|
||||
### 3. Area Events
|
||||
- Opening/closing
|
||||
- Status changes
|
||||
- Capacity updates
|
||||
|
||||
## Performance Optimization
|
||||
|
||||
### 1. Database Design
|
||||
- Efficient indexes
|
||||
- Compound keys
|
||||
- Query optimization
|
||||
|
||||
### 2. Processing Strategy
|
||||
- Batch updates
|
||||
- Chunked processing
|
||||
- Transaction management
|
||||
|
||||
### 3. Caching
|
||||
- [ ] Implement statistics caching
|
||||
- [ ] Add cache invalidation
|
||||
- [ ] Set up cache warming
|
||||
|
||||
## Future Enhancements
|
||||
1. [ ] Add trend analysis
|
||||
2. [ ] Implement forecasting
|
||||
3. [ ] Add historical graphs
|
||||
4. [ ] Create export tools
|
||||
5. [ ] Add benchmarking
|
||||
6. [ ] Implement alerts
|
||||
7. [ ] Add reporting
|
||||
8. [ ] Create dashboards
|
||||
|
||||
## Integration Points
|
||||
1. Areas System
|
||||
- Statistics collection
|
||||
- Event handling
|
||||
- Data validation
|
||||
|
||||
2. Parks System
|
||||
- Rollup processing
|
||||
- Performance tracking
|
||||
- Historical data
|
||||
|
||||
3. Operators System
|
||||
- Aggregation logic
|
||||
- Performance metrics
|
||||
- Trend analysis
|
||||
|
||||
## Security Considerations
|
||||
1. Data Validation
|
||||
- Range checks
|
||||
- Type validation
|
||||
- Relationship verification
|
||||
|
||||
2. Access Control
|
||||
- Update permissions
|
||||
- View restrictions
|
||||
- Audit logging
|
||||
|
||||
## Testing Strategy
|
||||
1. Unit Tests
|
||||
- [ ] Calculation accuracy
|
||||
- [ ] Event handling
|
||||
- [ ] Data validation
|
||||
|
||||
2. Integration Tests
|
||||
- [ ] Update propagation
|
||||
- [ ] Transaction handling
|
||||
- [ ] Event processing
|
||||
|
||||
3. Performance Tests
|
||||
- [ ] Large dataset handling
|
||||
- [ ] Concurrent updates
|
||||
- [ ] Batch processing
|
||||
|
||||
## Monitoring
|
||||
1. Performance Metrics
|
||||
- [ ] Update timing
|
||||
- [ ] Query performance
|
||||
- [ ] Cache hit rates
|
||||
|
||||
2. Error Tracking
|
||||
- [ ] Failed updates
|
||||
- [ ] Data inconsistencies
|
||||
- [ ] System alerts
|
||||
|
||||
3. Usage Analytics
|
||||
- [ ] Update frequency
|
||||
- [ ] Data access patterns
|
||||
- [ ] User interactions
|
||||
82
memory-bank/models/CompanyModel.md
Normal file
82
memory-bank/models/CompanyModel.md
Normal file
@@ -0,0 +1,82 @@
|
||||
# Operator Model Conversion
|
||||
|
||||
## Original Django Model Structure
|
||||
|
||||
### Company Model (Now Operator)
|
||||
```python
|
||||
class Company(TrackedModel):
|
||||
name = models.CharField(max_length=255)
|
||||
slug = models.SlugField(max_length=255, unique=True)
|
||||
website = models.URLField(blank=True)
|
||||
headquarters = models.CharField(max_length=255, blank=True)
|
||||
description = models.TextField(blank=True)
|
||||
total_parks = models.IntegerField(default=0)
|
||||
total_rides = models.IntegerField(default=0)
|
||||
```
|
||||
|
||||
### Manufacturer Model
|
||||
```python
|
||||
class Manufacturer(TrackedModel):
|
||||
name = models.CharField(max_length=255)
|
||||
slug = models.SlugField(max_length=255, unique=True)
|
||||
website = models.URLField(blank=True)
|
||||
headquarters = models.CharField(max_length=255, blank=True)
|
||||
description = models.TextField(blank=True)
|
||||
total_rides = models.IntegerField(default=0)
|
||||
total_roller_coasters = models.IntegerField(default=0)
|
||||
```
|
||||
|
||||
## Laravel Implementation Plan
|
||||
|
||||
### Database Migrations
|
||||
|
||||
1. Create operators table:
|
||||
```php
|
||||
Schema::create('operators', function (Blueprint $table) {
|
||||
$table->id();
|
||||
$table->string('name');
|
||||
$table->string('slug')->unique();
|
||||
$table->string('website')->nullable();
|
||||
$table->string('headquarters')->nullable();
|
||||
$table->text('description')->nullable();
|
||||
$table->integer('total_parks')->default(0);
|
||||
$table->integer('total_rides')->default(0);
|
||||
$table->timestamps();
|
||||
});
|
||||
```
|
||||
|
||||
2. Create manufacturers table:
|
||||
```php
|
||||
Schema::create('manufacturers', function (Blueprint $table) {
|
||||
$table->id();
|
||||
$table->string('name');
|
||||
$table->string('slug')->unique();
|
||||
$table->string('website')->nullable();
|
||||
$table->string('headquarters')->nullable();
|
||||
$table->text('description')->nullable();
|
||||
$table->integer('total_rides')->default(0);
|
||||
$table->integer('total_roller_coasters')->default(0);
|
||||
$table->timestamps();
|
||||
});
|
||||
```
|
||||
|
||||
### Models
|
||||
|
||||
1. Operator Model:
|
||||
- Implement Sluggable trait
|
||||
- Add relationships (parks)
|
||||
- Add statistics updating methods
|
||||
- Add slug history functionality
|
||||
|
||||
2. Manufacturer Model:
|
||||
- Implement Sluggable trait
|
||||
- Add relationships (rides)
|
||||
- Add statistics updating methods
|
||||
- Add slug history functionality
|
||||
|
||||
### Next Steps
|
||||
1. [ ] Create operators table migration
|
||||
2. [ ] Create manufacturers table migration
|
||||
3. [ ] Create Operator model
|
||||
4. [ ] Create Manufacturer model
|
||||
5. [ ] Implement statistics update methods
|
||||
104
memory-bank/models/LocationModel.md
Normal file
104
memory-bank/models/LocationModel.md
Normal file
@@ -0,0 +1,104 @@
|
||||
# Location Model
|
||||
|
||||
## Overview
|
||||
The Location model provides polymorphic location management for parks, areas, and other entities in ThrillWiki. It handles geocoding, coordinate management, and location-based search capabilities.
|
||||
|
||||
## Structure
|
||||
|
||||
### Database Table
|
||||
- Table Name: `locations`
|
||||
- Primary Key: `id` (bigint)
|
||||
- Polymorphic Fields: `locatable_type`, `locatable_id`
|
||||
- Timestamps: `created_at`, `updated_at`
|
||||
|
||||
### Fields
|
||||
- **Address Components**
|
||||
- `address` (string, nullable) - Street address
|
||||
- `city` (string) - City name
|
||||
- `state` (string, nullable) - State/province
|
||||
- `country` (string) - Country name
|
||||
- `postal_code` (string, nullable) - Postal/ZIP code
|
||||
|
||||
- **Coordinates**
|
||||
- `latitude` (decimal, 10,8) - Latitude coordinate
|
||||
- `longitude` (decimal, 11,8) - Longitude coordinate
|
||||
- `elevation` (decimal, 8,2, nullable) - Elevation in meters
|
||||
|
||||
- **Additional Details**
|
||||
- `timezone` (string, nullable) - Location timezone
|
||||
- `metadata` (json, nullable) - Additional location data
|
||||
- `is_approximate` (boolean) - Indicates if location is approximate
|
||||
- `source` (string, nullable) - Data source identifier
|
||||
|
||||
- **Geocoding**
|
||||
- `geocoding_data` (json, nullable) - Cached geocoding response
|
||||
- `geocoded_at` (timestamp, nullable) - Last geocoding timestamp
|
||||
|
||||
### Indexes
|
||||
- Coordinates: `(latitude, longitude)`
|
||||
- Location: `(country, state, city)`
|
||||
- Postal: `postal_code`
|
||||
|
||||
## Relationships
|
||||
|
||||
### Polymorphic
|
||||
- `locatable()` - Polymorphic relationship to parent model (Park, Area, etc.)
|
||||
|
||||
## Accessors & Mutators
|
||||
- `coordinates` - Returns [lat, lng] array
|
||||
- `formatted_address` - Returns formatted address string
|
||||
- `map_url` - Returns Google Maps URL
|
||||
|
||||
## Methods
|
||||
|
||||
### Location Management
|
||||
- `updateCoordinates(float $lat, float $lng)` - Update coordinates
|
||||
- `setAddress(array $components)` - Set address components
|
||||
- `geocode()` - Trigger geocoding refresh
|
||||
- `reverseGeocode()` - Get address from coordinates
|
||||
|
||||
### Queries
|
||||
- `scopeNearby($query, $lat, $lng, $radius)` - Find nearby locations
|
||||
- `scopeInBounds($query, $ne, $sw)` - Find locations in bounds
|
||||
- `scopeInCountry($query, $country)` - Filter by country
|
||||
- `scopeInState($query, $state)` - Filter by state
|
||||
- `scopeInCity($query, $city)` - Filter by city
|
||||
|
||||
### Calculations
|
||||
- `distanceTo($lat, $lng)` - Calculate distance to point
|
||||
- `bearingTo($lat, $lng)` - Calculate bearing to point
|
||||
|
||||
## Usage Examples
|
||||
|
||||
```php
|
||||
// Create location for park
|
||||
$park->location()->create([
|
||||
'address' => '123 Main St',
|
||||
'city' => 'Orlando',
|
||||
'state' => 'FL',
|
||||
'country' => 'USA',
|
||||
'latitude' => 28.538336,
|
||||
'longitude' => -81.379234
|
||||
]);
|
||||
|
||||
// Find parks within 50km
|
||||
$nearbyParks = Park::whereHas('location', function ($query) {
|
||||
$query->nearby(28.538336, -81.379234, 50);
|
||||
})->get();
|
||||
```
|
||||
|
||||
## Integration Points
|
||||
|
||||
### Services
|
||||
- GeocodeService - Address/coordinate lookup
|
||||
- LocationSearchService - Advanced location search
|
||||
|
||||
### Components
|
||||
- LocationSelector - Map-based location picker
|
||||
- LocationDisplay - Location visualization
|
||||
|
||||
## Notes
|
||||
- Coordinates use high precision for accuracy
|
||||
- Geocoding results are cached to reduce API calls
|
||||
- Polymorphic design allows reuse across models
|
||||
- Search methods use spatial indexes for performance
|
||||
164
memory-bank/models/ParkModel.md
Normal file
164
memory-bank/models/ParkModel.md
Normal file
@@ -0,0 +1,164 @@
|
||||
# Park Model Conversion
|
||||
|
||||
## Original Django Model Structure
|
||||
|
||||
### Park Model
|
||||
```python
|
||||
class Park(TrackedModel):
|
||||
# Status choices
|
||||
STATUS_CHOICES = [
|
||||
("OPERATING", "Operating"),
|
||||
("CLOSED_TEMP", "Temporarily Closed"),
|
||||
("CLOSED_PERM", "Permanently Closed"),
|
||||
("UNDER_CONSTRUCTION", "Under Construction"),
|
||||
("DEMOLISHED", "Demolished"),
|
||||
("RELOCATED", "Relocated"),
|
||||
]
|
||||
|
||||
# Basic info
|
||||
name = models.CharField(max_length=255)
|
||||
slug = models.SlugField(max_length=255, unique=True)
|
||||
description = models.TextField(blank=True)
|
||||
status = models.CharField(max_length=20, choices=STATUS_CHOICES, default="OPERATING")
|
||||
|
||||
# Location fields (GenericRelation)
|
||||
location = GenericRelation(Location)
|
||||
|
||||
# Details
|
||||
opening_date = models.DateField(null=True, blank=True)
|
||||
closing_date = models.DateField(null=True, blank=True)
|
||||
operating_season = models.CharField(max_length=255, blank=True)
|
||||
size_acres = models.DecimalField(max_digits=10, decimal_places=2, null=True)
|
||||
website = models.URLField(blank=True)
|
||||
|
||||
# Statistics
|
||||
average_rating = models.DecimalField(max_digits=3, decimal_places=2, null=True)
|
||||
ride_count = models.IntegerField(null=True)
|
||||
coaster_count = models.IntegerField(null=True)
|
||||
|
||||
# Relationships
|
||||
operator = models.ForeignKey(Operator, SET_NULL, null=True, related_name="parks")
|
||||
photos = GenericRelation(Photo)
|
||||
```
|
||||
|
||||
### ParkArea Model
|
||||
```python
|
||||
class ParkArea(TrackedModel):
|
||||
park = models.ForeignKey(Park, CASCADE, related_name="areas")
|
||||
name = models.CharField(max_length=255)
|
||||
slug = models.SlugField(max_length=255)
|
||||
description = models.TextField(blank=True)
|
||||
opening_date = models.DateField(null=True, blank=True)
|
||||
closing_date = models.DateField(null=True, blank=True)
|
||||
```
|
||||
|
||||
## Laravel Implementation Plan
|
||||
|
||||
### Enums
|
||||
1. Create ParkStatus enum with status options and color methods:
|
||||
```php
|
||||
enum ParkStatus: string {
|
||||
case OPERATING = 'OPERATING';
|
||||
case CLOSED_TEMP = 'CLOSED_TEMP';
|
||||
case CLOSED_PERM = 'CLOSED_PERM';
|
||||
case UNDER_CONSTRUCTION = 'UNDER_CONSTRUCTION';
|
||||
case DEMOLISHED = 'DEMOLISHED';
|
||||
case RELOCATED = 'RELOCATED';
|
||||
}
|
||||
```
|
||||
|
||||
### Database Migrations
|
||||
|
||||
1. Create parks table:
|
||||
```php
|
||||
Schema::create('parks', function (Blueprint $table) {
|
||||
$table->id();
|
||||
$table->string('name');
|
||||
$table->string('slug')->unique();
|
||||
$table->text('description')->nullable();
|
||||
$table->string('status', 20);
|
||||
|
||||
// Details
|
||||
$table->date('opening_date')->nullable();
|
||||
$table->date('closing_date')->nullable();
|
||||
$table->string('operating_season')->nullable();
|
||||
$table->decimal('size_acres', 10, 2)->nullable();
|
||||
$table->string('website')->nullable();
|
||||
|
||||
// Statistics
|
||||
$table->decimal('average_rating', 3, 2)->nullable();
|
||||
$table->integer('ride_count')->nullable();
|
||||
$table->integer('coaster_count')->nullable();
|
||||
|
||||
// Foreign keys
|
||||
$table->foreignId('operator_id')->nullable()->constrained('operators')->nullOnDelete();
|
||||
|
||||
$table->timestamps();
|
||||
});
|
||||
```
|
||||
|
||||
2. Create park_areas table:
|
||||
```php
|
||||
Schema::create('park_areas', function (Blueprint $table) {
|
||||
$table->id();
|
||||
$table->foreignId('park_id')->constrained()->cascadeOnDelete();
|
||||
$table->string('name');
|
||||
$table->string('slug');
|
||||
$table->text('description')->nullable();
|
||||
$table->date('opening_date')->nullable();
|
||||
$table->date('closing_date')->nullable();
|
||||
$table->timestamps();
|
||||
|
||||
$table->unique(['park_id', 'slug']);
|
||||
});
|
||||
```
|
||||
|
||||
### Models
|
||||
|
||||
1. Park Model:
|
||||
- Implement Sluggable trait
|
||||
- Add status color methods
|
||||
- Set up relationships (operator, areas, photos, location)
|
||||
- Add history tracking
|
||||
- Implement slug history functionality
|
||||
|
||||
2. ParkArea Model:
|
||||
- Implement Sluggable trait
|
||||
- Set up relationship with Park
|
||||
- Add history tracking
|
||||
- Implement slug history functionality
|
||||
|
||||
### Livewire Components
|
||||
|
||||
1. ParkListComponent:
|
||||
- Display parks with status badges
|
||||
- Filter by status
|
||||
- Sort functionality
|
||||
- Search by name
|
||||
|
||||
2. ParkFormComponent:
|
||||
- Create/edit park details
|
||||
- Location selection
|
||||
- Operator selection
|
||||
- Status management
|
||||
|
||||
3. ParkAreaComponent:
|
||||
- Manage park areas
|
||||
- Add/edit/delete areas
|
||||
- Sort/reorder areas
|
||||
|
||||
### Features to Implement
|
||||
1. Slug history tracking
|
||||
2. Location management
|
||||
3. Photo management
|
||||
4. Statistics calculation
|
||||
5. Area management
|
||||
6. Park status badges with colors
|
||||
|
||||
### Next Steps
|
||||
1. [ ] Create ParkStatus enum
|
||||
2. [ ] Create parks table migration
|
||||
3. [ ] Create park_areas table migration
|
||||
4. [ ] Create Park model
|
||||
5. [ ] Create ParkArea model
|
||||
6. [ ] Implement Livewire components
|
||||
122
memory-bank/models/UserModel.md
Normal file
122
memory-bank/models/UserModel.md
Normal file
@@ -0,0 +1,122 @@
|
||||
# User Model Conversion
|
||||
|
||||
## Original Django Model Structure
|
||||
|
||||
### User Model (extends AbstractUser)
|
||||
```python
|
||||
class User(AbstractUser):
|
||||
# Custom fields
|
||||
user_id = models.CharField(max_length=10, unique=True, editable=False)
|
||||
role = models.CharField(max_length=10, choices=['USER', 'MODERATOR', 'ADMIN', 'SUPERUSER'])
|
||||
is_banned = models.BooleanField(default=False)
|
||||
ban_reason = models.TextField(blank=True)
|
||||
ban_date = models.DateTimeField(null=True, blank=True)
|
||||
pending_email = models.EmailField(blank=True, null=True)
|
||||
theme_preference = models.CharField(max_length=5, choices=['light', 'dark'])
|
||||
```
|
||||
|
||||
### UserProfile Model
|
||||
```python
|
||||
class UserProfile:
|
||||
profile_id = models.CharField(max_length=10, unique=True, editable=False)
|
||||
user = models.OneToOneField(User, related_name='profile')
|
||||
display_name = models.CharField(max_length=50, unique=True)
|
||||
avatar = models.ImageField(upload_to='avatars/')
|
||||
pronouns = models.CharField(max_length=50, blank=True)
|
||||
bio = models.TextField(max_length=500, blank=True)
|
||||
|
||||
# Social media
|
||||
twitter = models.URLField(blank=True)
|
||||
instagram = models.URLField(blank=True)
|
||||
youtube = models.URLField(blank=True)
|
||||
discord = models.CharField(max_length=100, blank=True)
|
||||
|
||||
# Stats
|
||||
coaster_credits = models.IntegerField(default=0)
|
||||
dark_ride_credits = models.IntegerField(default=0)
|
||||
flat_ride_credits = models.IntegerField(default=0)
|
||||
water_ride_credits = models.IntegerField(default=0)
|
||||
```
|
||||
|
||||
## Laravel Implementation Plan
|
||||
|
||||
### Database Migrations
|
||||
|
||||
1. Extend users table (`database/migrations/[timestamp]_add_user_fields.php`):
|
||||
```php
|
||||
Schema::table('users', function (Blueprint $table) {
|
||||
$table->string('user_id', 10)->unique();
|
||||
$table->enum('role', ['USER', 'MODERATOR', 'ADMIN', 'SUPERUSER'])->default('USER');
|
||||
$table->boolean('is_banned')->default(false);
|
||||
$table->text('ban_reason')->nullable();
|
||||
$table->timestamp('ban_date')->nullable();
|
||||
$table->string('pending_email')->nullable();
|
||||
$table->enum('theme_preference', ['light', 'dark'])->default('light');
|
||||
});
|
||||
```
|
||||
|
||||
2. Create profiles table (`database/migrations/[timestamp]_create_profiles_table.php`):
|
||||
```php
|
||||
Schema::create('profiles', function (Blueprint $table) {
|
||||
$table->id();
|
||||
$table->string('profile_id', 10)->unique();
|
||||
$table->foreignId('user_id')->constrained()->onDelete('cascade');
|
||||
$table->string('display_name', 50)->unique();
|
||||
$table->string('avatar')->nullable();
|
||||
$table->string('pronouns', 50)->nullable();
|
||||
$table->text('bio')->nullable();
|
||||
|
||||
// Social media
|
||||
$table->string('twitter')->nullable();
|
||||
$table->string('instagram')->nullable();
|
||||
$table->string('youtube')->nullable();
|
||||
$table->string('discord', 100)->nullable();
|
||||
|
||||
// Stats
|
||||
$table->integer('coaster_credits')->default(0);
|
||||
$table->integer('dark_ride_credits')->default(0);
|
||||
$table->integer('flat_ride_credits')->default(0);
|
||||
$table->integer('water_ride_credits')->default(0);
|
||||
|
||||
$table->timestamps();
|
||||
});
|
||||
```
|
||||
|
||||
### Model Implementation
|
||||
|
||||
1. User Model (`app/Models/User.php`):
|
||||
- Extend Laravel's base User model
|
||||
- Add custom attributes
|
||||
- Add relationship to Profile
|
||||
- Add role management methods
|
||||
- Add ban management methods
|
||||
|
||||
2. Profile Model (`app/Models/Profile.php`):
|
||||
- Create new model
|
||||
- Add relationship to User
|
||||
- Add avatar handling methods
|
||||
- Add credit management methods
|
||||
|
||||
### Livewire Components
|
||||
1. ProfileComponent - Handle profile management
|
||||
2. AvatarUploadComponent - Handle avatar uploads
|
||||
3. UserSettingsComponent - Handle user settings/preferences
|
||||
4. UserBanComponent - For moderator use to handle bans
|
||||
|
||||
### Services
|
||||
1. UserService - Business logic for user management
|
||||
2. ProfileService - Business logic for profile management
|
||||
3. AvatarService - Handle avatar generation and storage
|
||||
|
||||
### Next Steps
|
||||
1. [ ] Create user fields migration
|
||||
2. [ ] Create profiles table migration
|
||||
3. [ ] Enhance User model with new fields and methods
|
||||
4. [ ] Create Profile model
|
||||
5. [ ] Implement initial Livewire components for profile management
|
||||
|
||||
### Notes
|
||||
- Will use Laravel's built-in authentication (already scaffolded)
|
||||
- Email verification will be handled by Laravel's built-in features
|
||||
- Password reset functionality will use Laravel's default implementation
|
||||
- Will implement custom avatar generation similar to Django version
|
||||
50
memory-bank/productContext.md
Normal file
50
memory-bank/productContext.md
Normal file
@@ -0,0 +1,50 @@
|
||||
# ThrillWiki Laravel+Livewire Conversion
|
||||
|
||||
## Project Overview
|
||||
ThrillWiki is being converted from a Django application to a Laravel application using Livewire for dynamic frontend functionality. The original Django project contains several key modules:
|
||||
|
||||
- Accounts (User management)
|
||||
- Analytics
|
||||
- Companies
|
||||
- Core
|
||||
- Designers
|
||||
- Email Service
|
||||
- History/History Tracking
|
||||
- Location
|
||||
- Media
|
||||
- Moderation
|
||||
- Parks
|
||||
- Reviews
|
||||
- Rides
|
||||
- Search
|
||||
- Wiki
|
||||
|
||||
## Technology Stack Transition
|
||||
- From: Django (Python) with server-side templates
|
||||
- To: Laravel (PHP) with Livewire for reactive components
|
||||
|
||||
## Core Features to Convert
|
||||
1. User authentication and management
|
||||
2. Park and ride management
|
||||
3. Review system
|
||||
4. Media handling
|
||||
5. Search functionality
|
||||
6. History tracking
|
||||
7. Location services
|
||||
8. Company management
|
||||
9. Moderation tools
|
||||
10. Analytics
|
||||
|
||||
## Why Laravel + Livewire?
|
||||
- Maintains server-side rendering approach
|
||||
- Provides reactive UI components without full JavaScript framework
|
||||
- Rich ecosystem for PHP development
|
||||
- Simpler deployment model compared to SPA
|
||||
- Built-in authentication and authorization
|
||||
|
||||
## Project Goals
|
||||
1. Feature parity with Django version
|
||||
2. Improved performance
|
||||
3. Maintainable codebase
|
||||
4. Progressive enhancement
|
||||
5. Mobile-friendly interface
|
||||
50
memory-bank/prompts/ContinuationCommand.md
Normal file
50
memory-bank/prompts/ContinuationCommand.md
Normal file
@@ -0,0 +1,50 @@
|
||||
# ThrillWiki Development Continuation Command
|
||||
|
||||
Use this command to continue development in a new chat:
|
||||
|
||||
```
|
||||
Continue ThrillWiki Laravel+Livewire development, focusing on the Location System implementation. The project is at /Users/talor/ThrillWiki/laravel.
|
||||
|
||||
Key Memory Bank files to review:
|
||||
1. memory-bank/activeContext.md - Current progress and next steps
|
||||
2. memory-bank/features/LocationSystem.md - System design and implementation plan
|
||||
3. memory-bank/features/StatisticsRollup.md - Statistics integration points
|
||||
4. memory-bank/features/StatisticsCaching.md - Caching strategy
|
||||
|
||||
Current progress:
|
||||
- Documented Location System design
|
||||
- Created locations table migration
|
||||
- Set up Memory Bank documentation
|
||||
|
||||
Next steps:
|
||||
1. Create Location model with polymorphic relationships
|
||||
2. Implement HasLocation trait
|
||||
3. Develop GeocodeService
|
||||
4. Build LocationSearchService
|
||||
5. Create Livewire components
|
||||
|
||||
Follow Memory Bank documentation practices:
|
||||
- Prefix all tool use with [MEMORY BANK: ACTIVE]
|
||||
- Document before implementing
|
||||
- Update activeContext.md after each step
|
||||
- Create feature documentation first
|
||||
- Document technical decisions
|
||||
|
||||
The project uses:
|
||||
- Laravel for backend
|
||||
- Livewire for components
|
||||
- MySQL for database
|
||||
- Memory Bank for documentation
|
||||
|
||||
Continue implementation following the established patterns and maintaining comprehensive documentation.
|
||||
```
|
||||
|
||||
This command provides:
|
||||
1. Project context
|
||||
2. Memory Bank locations
|
||||
3. Current progress
|
||||
4. Next steps
|
||||
5. Development practices
|
||||
6. Technical stack
|
||||
|
||||
Use this to ensure continuity and maintain our documentation-first approach in the next development session.
|
||||
69
memory-bank/prompts/LocationSystemContinuation.md
Normal file
69
memory-bank/prompts/LocationSystemContinuation.md
Normal file
@@ -0,0 +1,69 @@
|
||||
# ThrillWiki Development Continuation Prompt
|
||||
|
||||
Continue the development of ThrillWiki's Location System implementation. The project is a Laravel+Livewire application for managing theme parks, currently being converted from Django.
|
||||
|
||||
## Current Progress
|
||||
|
||||
We have:
|
||||
1. Documented the Location System design in `memory-bank/features/LocationSystem.md`
|
||||
2. Created the locations table migration in `database/migrations/2024_02_23_235000_create_locations_table.php`
|
||||
|
||||
## Next Implementation Steps
|
||||
|
||||
1. Create the Location model with:
|
||||
- Polymorphic relationships
|
||||
- Coordinate handling
|
||||
- Geocoding integration
|
||||
- Distance calculations
|
||||
|
||||
2. Implement the HasLocation trait for:
|
||||
- Location relationships
|
||||
- Coordinate accessors
|
||||
- Distance methods
|
||||
- Map integration
|
||||
|
||||
3. Create the GeocodeService for:
|
||||
- Address lookup
|
||||
- Coordinate validation
|
||||
- Batch processing
|
||||
- Cache management
|
||||
|
||||
4. Implement the LocationSearchService for:
|
||||
- Distance-based search
|
||||
- Boundary queries
|
||||
- Clustering support
|
||||
- Performance optimization
|
||||
|
||||
5. Create Livewire components for:
|
||||
- Location selection
|
||||
- Map integration
|
||||
- Address search
|
||||
- Coordinate picking
|
||||
|
||||
## Project Structure
|
||||
|
||||
Key files and directories:
|
||||
- `memory-bank/features/LocationSystem.md` - System documentation
|
||||
- `app/Models/` - Model implementations
|
||||
- `app/Traits/` - Shared traits
|
||||
- `app/Services/` - Service classes
|
||||
- `app/Livewire/` - Livewire components
|
||||
- `resources/views/livewire/` - Component views
|
||||
|
||||
## Development Context
|
||||
|
||||
The system uses:
|
||||
- Laravel for backend
|
||||
- Livewire for components
|
||||
- MySQL for database
|
||||
- Memory Bank for documentation
|
||||
|
||||
## Next Steps
|
||||
|
||||
1. Create the Location model
|
||||
2. Implement HasLocation trait
|
||||
3. Develop geocoding service
|
||||
4. Build search functionality
|
||||
5. Create Livewire components
|
||||
|
||||
Please continue implementing these features following the established patterns and maintaining comprehensive documentation in the Memory Bank.
|
||||
68
memory-bank/prompts/MemoryBankInstructions.md
Normal file
68
memory-bank/prompts/MemoryBankInstructions.md
Normal file
@@ -0,0 +1,68 @@
|
||||
# Memory Bank Access Instructions
|
||||
|
||||
To continue development with full context, please review these key Memory Bank files in order:
|
||||
|
||||
1. `memory-bank/activeContext.md`
|
||||
- Current development phase
|
||||
- Progress tracking
|
||||
- Next steps
|
||||
- Technical decisions
|
||||
- Issues to address
|
||||
|
||||
2. `memory-bank/features/LocationSystem.md`
|
||||
- System design
|
||||
- Component structure
|
||||
- Implementation details
|
||||
- Integration points
|
||||
- Future enhancements
|
||||
|
||||
3. `memory-bank/features/StatisticsRollup.md`
|
||||
- Statistics system design
|
||||
- Integration points
|
||||
- Performance considerations
|
||||
|
||||
4. `memory-bank/features/StatisticsCaching.md`
|
||||
- Caching strategy
|
||||
- Performance optimization
|
||||
- Integration points
|
||||
|
||||
## Development Process
|
||||
|
||||
1. Always prefix tool use with `[MEMORY BANK: ACTIVE]`
|
||||
2. Document changes in Memory Bank before implementation
|
||||
3. Update `activeContext.md` after each major step
|
||||
4. Create feature documentation before implementation
|
||||
5. Document technical decisions and their rationale
|
||||
|
||||
## Next Development Session
|
||||
|
||||
1. Review `memory-bank/prompts/LocationSystemContinuation.md`
|
||||
2. Check `activeContext.md` for current status
|
||||
3. Implement next steps following documented design
|
||||
4. Maintain Memory Bank documentation
|
||||
5. Update progress tracking
|
||||
|
||||
## Key Files
|
||||
|
||||
The following files contain essential context:
|
||||
|
||||
```
|
||||
memory-bank/
|
||||
├── activeContext.md # Current state and next steps
|
||||
├── features/
|
||||
│ ├── LocationSystem.md # Location system design
|
||||
│ ├── StatisticsRollup.md # Statistics system design
|
||||
│ └── StatisticsCaching.md # Caching implementation
|
||||
└── prompts/
|
||||
└── LocationSystemContinuation.md # Next steps
|
||||
```
|
||||
|
||||
## Development Command
|
||||
|
||||
To continue development in a new chat, use:
|
||||
|
||||
```
|
||||
Continue ThrillWiki Laravel+Livewire development, implementing the Location System as documented in memory-bank/features/LocationSystem.md. Current progress and next steps are in memory-bank/prompts/LocationSystemContinuation.md. Follow Memory Bank documentation practices from memory-bank/prompts/MemoryBankInstructions.md.
|
||||
```
|
||||
|
||||
This will ensure continuity and maintain our documentation-first approach.
|
||||
Reference in New Issue
Block a user