feat: Add Actix-web integration with custom schema support

[Penivera]

PR: Actix-Web Integration with Custom Schema Support

Overview

This PR adds native Actix-web integration to SeaORM Pro, allowing it to be used as a fully reusable library module in any Actix application. Additionally, it introduces support for custom GraphQL schemas, enabling integration with external Sea-ORM entities instead of just seaorm-pro's built-in ones.

What's Included

1. SeaOrmProActixConfigurator - Reusable Library API

Located in src/actix_integration.rs, this module provides:

• SeaOrmProActixConfigurator: Cloneable, thread-safe configurator for mounting admin routes
• SeaOrmProActixOptions: Builder-pattern options with sensible defaults
• One-line integration: .configure(cfg) mounts all admin routes

2. Feature-Gated Architecture

• New actix-integration feature in Cargo.toml
• Zero forced dependencies on Loco/Axum when using Actix only
• Default loco-app feature keeps standalone server behavior unchanged
• Enables clean multi-consumer library architecture

3. Custom Schema Support

• New with_custom_schema(schema) builder method
• Allows using custom Sea-ORM entities instead of built-in Django-style users table
• Consumers can build GraphQL schemas using seaography with their own entities
• Fully backward compatible - defaults to sea-orm-pro's built-in entities

4. Complete Authentication Layer

• JWT token generation/validation via jsonwebtoken crate
• Bcrypt password hashing/verification via bcrypt crate
• Bearer token extraction from Authorization headers
• Protected GraphQL execution with user context injection

5. GraphQL Admin Interface

• GET /admin/graphql - Interactive playground with auth token injection
• POST /admin/auth/login - JWT token generation with credentials
• GET /admin/user/current - Current user profile (protected)
• POST /admin/graphql - GraphQL query execution (protected)
• GET /admin/config - Admin configuration (public)

6. Comprehensive Documentation

• README.md: Updated with Actix integration examples
• CUSTOM_ENTITIES.md: Complete guide on using custom entities (120+ lines)
• Includes troubleshooting, examples, and best practices

Usage Examples

Simple Default Setup (1-line)

use sea_orm_pro_backend::actix_integration::{SeaOrmProActixConfigurator, SeaOrmProActixOptions};

let admin = SeaOrmProActixConfigurator::new(
    SeaOrmProActixOptions::new(db, secret_key)
)?;

App::new()
    .configure(move |cfg| admin.configure(cfg))
    .configure(other_routes)

Custom Entities Setup

let custom_schema = build_my_schema(db.clone())?;

let admin = SeaOrmProActixConfigurator::new(
    SeaOrmProActixOptions::new(db, secret_key)
        .with_custom_schema(custom_schema)
)?;

Testing

✅ Compilation: cargo check passes in v2 workspace
✅ Feature Isolation: Actix module doesn't pull Loco/Axum deps
✅ Backward Compatibility: Existing standalone app still works
✅ Integration Test: Successfully mounted alongside v2 routes

How to Test Locally

1. Change Feature Flags in v2/Cargo.toml:

   sea-orm-pro-backend = { 
       path = "../sea-orm-pro", 
       default-features = false, 
       features = ["actix-integration", "sqlx-postgres"]
   }

2. Build and Run:

   cargo check --manifest-path v2/Cargo.toml
   cargo run --manifest-path v2/Cargo.toml

3. Test Endpoints:

   # Seed admin user
   sqlite3 v2/db.sqlite "
   INSERT OR REPLACE INTO users_user (id, email, password, username, is_email_verified)
   VALUES (1, 'admin@test.com', '\$2b\$12\$...bcrypt_hash...', 'admin', 1);"
   
   # Login
   curl -X POST http://localhost:8080/admin/auth/login \
     -H "Content-Type: application/json" \
     -d '{"email":"admin@test.com","password":"demo"}'
   
   # Use token on protected route
   TOKEN="eyJ0eXAi..."
   curl -H "Authorization: Bearer $TOKEN" \
     http://localhost:8080/admin/user/current

Files Changed

File	Type	Lines	Description
src/actix_integration.rs	NEW	438	Core Actix module with all handlers
CUSTOM_ENTITIES.md	NEW	160+	Complete custom entities guide
README.md	MODIFIED	+50	Actix integration usage examples
Cargo.toml	MODIFIED	+4/-2	Feature gates + dependencies
src/lib.rs	MODIFIED	+2	Conditional module exports

Benefits

1. Reusability: SeaORM Pro becomes a true library, not just a standalone app
2. Flexibility: Custom entities replace the need to regenerate sea-orm-pro
3. Non-Breaking: Existing standalone app continues to work unchanged
4. Feature-Gated: No forced dependencies on frameworks you don't use
5. Production-Ready: JWT + bcrypt auth, configurable limits, error handling

Migration Path

• Existing Users: No changes needed, everything works as before
• Library Consumers: Add feature flag, instantiate configurator, call .configure()
• Custom Entity Users: Build schema with seaography, pass to with_custom_schema()

Related Issues

Closes #<ISSUE_NUMBER>

Checklist

• Code compiles without errors
• Feature-gated properly (no forced Loco/Axum for Actix users)
• Backward compatible (default uses sea-orm-pro entities)
• Tested with v2 integration
• Documentation includes examples
• Custom schema support verified
• JWT auth layer working
• GraphQL playground functioning

Reviewers

@SeaQL/team - Please review for:

1. Architecture alignment with SeaORM ecosystem
2. Security of JWT/bcrypt implementation
3. API design for SeaOrmProActixOptions and SeaOrmProActixConfigurator
4. Documentation clarity and completeness

---

Additional Notes

This feature brings SeaORM Pro inline with modern Rust library design patterns:

• Works as a library (via feature gates)
• Supports multiple frameworks via alternate consumers (currently Actix, could add others)
• Fully self-contained authentication (no middleware magic)
• Flexible schema building (custom entities without regeneration)

The implementation prioritizes developer experience and reusability while maintaining the existing standalone application behavior.