Update Rules for Ammend

[58bits]

Just a suggestion, but you might want to consider updating your $updateRules used during an amend (user update) to include an extra option that checks for a unique username and email address, with the exception of the current user id. This would allow a user to change their email address or username, as long as they are still unique. As the rules are at the moment, there is no 'unique' check, and unless special rules are passed to ammend, a user could change their username to be the same as another user (like admin).

$updateRules = array(
            'username'=> 'required|alpha_dash|unique:users,username,'. $this->id,
            'email' => 'required|email|unique:users,email,'. $this->id,
            'password' => 'between:4,11|confirmed',
            'password_confirmation' => 'between:4,11',
            );

[nightowl77]

We are working on this issue. We actually want to completely do away with $updateRules, so that Confide works the same way Eloquent works (eloquent has no concept of $updateRules, you just supply $rules and everything works). The idea is that Confide encapsulates and hides these complexities from the programmer, which would then cut down on the amount of code and documentation required.

Please see #124 for a discussion about this.

Right now I am waiting for a pull request to be accepted for Ardent here (laravel-ardent/ardent#86). Once that is accepted I want to work on this "encapsulates and hides these complexities" version of Confide.

[58bits]

Great - glad to hear you're working on this!

[andrew13]

👍