Modello Utente

use Escalated\Laravel\Contracts\HasTickets;
use Escalated\Laravel\Contracts\Ticketable;

class User extends Authenticatable implements Ticketable
{
    use HasFactory, HasTickets, Notifiable;
}

Il trait HasTickets fornisce una relazione tickets() e metodi helper sul modello utente.

class User < ApplicationRecord
  include Escalated::Ticketable
end

Django utilizza AUTH_USER_MODEL automaticamente. Non sono necessarie modifiche al tuo modello utente.

// The AdonisJS package uses your configured userModel
// from config/escalated.ts — no trait needed.
// Users are linked via the foreign key on the tickets table.

Configura il percorso di importazione del modello utente in config/escalated.ts sotto userModel.

use Escalated\Laravel\Contracts\HasTickets;
use Escalated\Laravel\Contracts\Ticketable;

class User extends Authenticatable implements Ticketable
{
    use HasFactory, HasTickets, Notifiable;
}

Filament utilizza la stessa configurazione del modello utente di escalated-laravel poiché è un wrapper del pacchetto Laravel.

WordPress utilizza il suo sistema utente nativo automaticamente. I ticket sono collegati agli ID utente WordPress -- non sono necessarie modifiche al tuo modello utente. Il supporto per i ticket guest è disponibile per gli utenti non autenticati tramite token di accesso sicuri.

The Flutter package retrieves user data from your backend API via the auth hooks system. There is no local User model to configure — authentication and user resolution happen server-side.

Auth Hooks

Override AuthHooks to plug in your own authentication logic:

class MyAuthHooks extends AuthHooks {
  @override
  Future<AuthResult> onLogin(String email, String password) async {
    // Call your auth API, return token + user info
    final response = await myAuthService.login(email, password);
    return AuthResult(
      token: response.token,
      user: AuthUser(
        name: response.user.name,
        email: response.user.email,
      ),
    );
  }

  @override
  Future<void> onLogout() async {
    await myAuthService.logout();
  }
}

Pass your hooks to the config:

EscalatedConfig(
  apiBaseUrl: 'https://yourapp.com/support/api/v1',
  authHooks: MyAuthHooks(),
)

Note: The package sends a Bearer token with every API request. Your backend's Ticketable user model handles the rest.

The React Native package retrieves user data from your backend API via the auth hooks system. There is no local User model to configure — authentication and user resolution happen server-side.

Auth Hooks

Provide custom auth callbacks through the provider config:

import { EscalatedProvider, AuthHooks } from '@escalated-dev/escalated-react-native';

const customHooks: AuthHooks = {
  onLogin: async (email, password) => {
    const response = await myAuthService.login(email, password);
    return {
      token: response.token,
      user: { name: response.user.name, email: response.user.email },
    };
  },
  onLogout: async () => {
    await myAuthService.logout();
  },
};

export default function App() {
  return (
    <EscalatedProvider config={{ apiBaseUrl: 'https://yourapp.com/support/api/v1', authHooks: customHooks }}>
      {/* ... */}
    </EscalatedProvider>
  );
}

Note: The package sends a Bearer token with every API request. Your backend's Ticketable user model handles the rest.