Don't force team registration

I'd also be very interested to get this answered without breaking future updates...

Here is what I found so far:

• the concept of a team is entirely optional in spark (users can delete a team after the initial cration and everyhting will work normally) - only the validation during registration breaks it
• unfortunately 'required' is hardcoded in validation during registraion in vendor\laravel\spark\src\Interactions\Auth\CreateUser.php

as follows:

    public function validator($request)
    {
        $validator = $this->baseValidator($request);

        $validator->sometimes('team', 'required|max:255', function ($input) {
            return Spark::usesTeams() && ! isset($input['invitation']);
        });

        return $validator;

If you remove the 'required' you are done, but this might break any future updates - which is exactly the tricky point...

EDIT: there is also a middleware reminding/ redirecting people to create a team if they have none, but it can be disabled easily.

Extend the original CreateUser class and override the validator method. Then in your AppServiceProviders register method, add this line:

app()->bind('Laravel\Spark\Contracts\Interactions\Auth\CreateUser', YourNewCreateUserClass::class, true);

This won't keep the team from being created, but will in actuality create a nameless team.

An optimal approach would be to not have any breaking changes. Creating a nameless team wouldn't make sense either.

Bit of a necrobump but I figured out a workaround after I asked the same question on /r/laravel: https://www.reddit.com/r/laravel/comments/4l3iyo/adapting_spark_teams_to_fit_my_use_case/

You need to copy Register and CreateUser classes from Laravel\Spark\Interactions\Auth and remove lines:

• Register: 58
• CreateUser: 20-22

You then need to bind your new interactions to the container. I did mine in my SparkServiceProvider@register:

$this->app->bind('Laravel\Spark\Contracts\Interactions\Auth\Register', Register::class);
$this->app->bind('Laravel\Spark\Contracts\Interactions\Auth\CreateUser', CreateUser::class);

Remove the input field in the common registration template. Now you need to remove the hasTeam middleware from your own RouteServiceProvider to prevent the missing-team redirect after registering.

I also have my own user creator/validator classes swapped so I'm not sure if you'll need to do that or not to remove any teamname required validation.

@Hedam @EventFellows

If anyone happens to come across this because they are seeing the missing-team view and url, this is because there is the hasTeam middleware being passed in your RouteServiceProvider. You can just remove that from the middleware array for the group:

    protected function mapWebRoutes(Router $router)
    {
        $router->group([
            'namespace' => $this->namespace, 'middleware' => ['web', 'hasTeam'],
        ], function ($router) {
            require base_path('routes/web.php');
        });
    }

This is in 5.4 again in the App\Providers\RouteServiceProvider

deactivating the middleware still works in spark 6... thanks @plushyObject ;)