Modelo de Usuario

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

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

O trait HasTickets fornece um relacionamento tickets() e metodos auxiliares no modelo de usuario.

class User < ApplicationRecord
  include Escalated::Ticketable
end

O Django utiliza AUTH_USER_MODEL automaticamente. Nenhuma alteracao e necessaria no seu modelo de usuario.

// 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.

Configure o caminho de importacao do modelo de usuario em config/escalated.ts na chave userModel.

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

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

O Filament utiliza a mesma configuracao de modelo de usuario do escalated-laravel, pois e um wrapper de pacote Laravel.

O WordPress utiliza seu sistema de usuarios nativo automaticamente. Tickets sao vinculados aos IDs de usuario do WordPress -- nenhuma alteracao no seu modelo de usuario e necessaria. Suporte a tickets de visitante esta disponivel para usuarios nao autenticados via tokens de acesso seguros.

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.