6 |--------------------------------------------------------------------------
8 |--------------------------------------------------------------------------
10 | This is the ID of your Discord application.
14 'client_id' => env('LARASCORD_CLIENT_ID', null),
17 |--------------------------------------------------------------------------
19 |--------------------------------------------------------------------------
21 | This is the secret of your Discord application.
25 'client_secret' => env('LARASCORD_CLIENT_SECRET', null),
28 |--------------------------------------------------------------------------
30 |--------------------------------------------------------------------------
32 | This is the grant type of your Discord application. It must be set to "authorization_code".
36 'grant_type' => env('LARASCORD_GRANT_TYPE', 'authorization_code'),
39 |--------------------------------------------------------------------------
41 |--------------------------------------------------------------------------
43 | This is the URI that Discord will redirect to after the user authorizes your application.
47 'redirect_uri' => env('APP_URL', 'http://localhost:8000') . '/' . env('LARASCORD_PREFIX', 'larascord') . '/callback',
50 |--------------------------------------------------------------------------
52 |--------------------------------------------------------------------------
54 | These are the OAuth2 scopes of your Discord application.
58 'scopes' => env('LARASCORD_SCOPE', 'identify'),
61 |--------------------------------------------------------------------------
63 |--------------------------------------------------------------------------
65 | This is the prefix that Larascord will use for its routes.
66 | For example, the prefix "larascord" will result in the route "https://domain.com/larascord/login".
70 'prefix' => env('LARASCORD_PREFIX', 'larascord'),
73 |--------------------------------------------------------------------------
74 | OAuth2 Prompt - "none" or "consent"
75 |--------------------------------------------------------------------------
77 | The prompt controls how the authorization flow handles existing authorizations.
78 | If a user has previously authorized your application with the requested scopes and prompt is set to consent,
79 | it will request them to re-approve their authorization.
80 | If set to none, it will skip the authorization screen and redirect them back to your redirect URI without requesting their authorization.
87 |--------------------------------------------------------------------------
89 |--------------------------------------------------------------------------
91 | These are the error messages that will be display to the user if there is an error.
96 'missing_code' => 'The authorization code is missing.',
97 'invalid_code' => 'The authorization code is invalid.',
98 'authorization_failed' => 'The authorization failed.',
99 'missing_email' => 'Couldn\'t get your e-mail address. Make sure you are using the <strong>identify&email</strong> scopes.',
100 'invalid_user' => 'The user ID doesn\'t match the logged-in user.',
101 'database_error' => 'There was an error with the database. Please try again later.',