사용자 모델

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

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

HasTickets 트레이트는 사용자 모델에 tickets() 관계 및 헬퍼 메서드를 제공합니다.

class User < ApplicationRecord
  include Escalated::Ticketable
end

Django는 AUTH_USER_MODEL을 자동으로 사용합니다. 사용자 모델을 변경할 필요가 없습니다.

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

config/escalated.ts의 userModel에서 사용자 모델 임포트 경로를 설정하세요.

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

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

Filament는 escalated-laravel 패키지의 래퍼이므로 동일한 사용자 모델 설정을 사용합니다.

WordPress는 네이티브 사용자 시스템을 자동으로 사용합니다. 티켓은 WordPress 사용자 ID에 연결되므로 사용자 모델을 변경할 필요가 없습니다. 게스트 티켓 지원은 보안 액세스 토큰을 통해 미인증 사용자에게도 제공됩니다.

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.