Remove the routes, views and translations and set it as an option in the setup, or make a vendor publishing

[black-bits]

Remove the routes, views and translations and set it as an option in the setup, or make a vendor publishing

[bartmcleod]

I can not reproduce this. Can list routes with the command. Version: "black-bits/laravel-cognito-auth": "dev-defaultProvider"

From

   {
       "type": "vcs",
       "url": "https://github.com/jaytaph/laravel-cognito-auth"
   }

[MarcosSchlickmann]

I have this same issue on a fresh start. Perhaps it's because I'm on Laravel 8?

[MarcosSchlickmann]

It is because of the version. I agree with @phackwer, these routes should be optional or customizable.

In Laravel 8 the authentication scaffolding was changed. I generated it through laravel/breeze and these are the generated files in app/Http/Controllers/Auth:

AuthenticatedSessionController.php
ConfirmablePasswordController.php
EmailVerificationNotificationController.php
EmailVerificationPromptController.php
NewPasswordController.php
PasswordResetLinkController.php
RegisteredUserController.php
VerifyEmailController.php

In Laravel 6 these are the files scaffolded by laravel/ui in app/Http/Controllers/Auth:

ConfirmPasswordController.php
ForgotPasswordController.php
LoginController.php
RegisterController.php
ResetPasswordController.php
VerificationController.php

[phackwer]

@MarcosSchlickmann I've made a fork to comment the routes from the service provider of the package till someone answer this request.

https://github.com/4cme/laravel-cognito-auth

In my case we have an app so the laravel is all API oriented, no views there other than the jsons. I think that it the best approach in this case would be to isolate screens/views and routes as an isolated package that uses the core of the package to talk to cognito.

[phackwer]

BTW: the forked package also fixes the error I had on 104.