Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confide 4.0 #209

Merged
merged 126 commits into from
Jul 20, 2014
Merged

Confide 4.0 #209

merged 126 commits into from
Jul 20, 2014

Conversation

Zizaco
Copy link
Owner

@Zizaco Zizaco commented Jan 30, 2014

Confide 4.0

This will be a huge update where all the codebase are going to be reviewed. Some methods may change, the generators are going to be improved in order to match some best practices out there (like repositories and separated validator classes).
The 'laravelbook/ardent' dependency will be dropped.

If you have a legacy project that uses Confide, don't worry. You will be always able to specify a previous version in your composer.json file ;)

@andrew13
Copy link
Collaborator

Awesome! I'll start testing.

@Zizaco
Copy link
Owner Author

Zizaco commented Jan 30, 2014

Is still a very early stage, but I think that this restructuring will help
a lot. (:

2014-01-30 Andrew notifications@github.com:

Awesome!

Reply to this email directly or view it on GitHubhttps://github.com//pull/209#issuecomment-33660600
.

@byordereurope
Copy link
Contributor

Thumbs up for this move, keep up the good work.

…ce in order to be able to implement other compatible services.
…rviceProvider in order to make the main Confide class available to the application.
@Zizaco Zizaco mentioned this pull request Feb 1, 2014
@Zizaco
Copy link
Owner Author

Zizaco commented Jul 14, 2014

@mapb1990 Não, o método login() chamado pertence a classe UserRepository, que também é gerada pelo Confide. https://github.com/Zizaco/confide/blob/huge-update/src/views/generators/repository.blade.php#L49

@delsdog
Copy link

delsdog commented Jul 14, 2014

tried the ~4.0 version, but with no joy, composer can't seem to find the package, I presume there is some updating in progress? If 4.0 final is in the next few days then I can wait.

@GrahamCampbell
Copy link
Contributor

@delsdog set your minimum stability below stable.

@delsdog
Copy link

delsdog commented Jul 14, 2014

@GrahamCampbell thanks that seemed to do the trick.

@Zizaco
Copy link
Owner Author

Zizaco commented Jul 14, 2014

If you have any issues using the beta, please don't hesitate to open a new issue. (:

Also, please state that you are using the 4.0 beta

@Zizaco
Copy link
Owner Author

Zizaco commented Jul 17, 2014

Release Notes

Version 4.0.0 Beta 2

  • UserValidator now adds errors to a existing MessageBag instead of replacing it.
  • Password reset token will expire after 7 days.
  • Added support for custom connections using the $connection attribute of the model.
  • Password reset requests are deleted after being used.

Zizaco and others added 3 commits July 17, 2014 22:28
ing information about cleaning the password_confirmation attribute of user.
Improve default UserValidator behavior[4.0.0 beta 2]
@GrahamCampbell
Copy link
Contributor

Should you move the stuff from the master branch to a "3.2" branch, then merge this now? This should ensure we don't have any last minute branch aliasing issues tomorrow.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 267bd49 on huge-update into * on master*.

@Zizaco
Copy link
Owner Author

Zizaco commented Jul 20, 2014

Release Notes

Version 4.0.0 Beta 3

  • Now you can customize how long will take for a password reset request to expire (default to 7 hours).
  • Reordered validations
  • Now all validations are called even if one of them fails. So all validation messages are sent at once.
  • validateIsUnique method now sends key to attachErrorMsg and also check for errors on each $identity field at once

Also merged into master :)

Zizaco added a commit that referenced this pull request Jul 20, 2014
@Zizaco Zizaco merged commit 3f3e276 into master Jul 20, 2014
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling d4ffb97 on huge-update into * on master*.

@Zizaco Zizaco deleted the huge-update branch July 20, 2014 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet