-
Notifications
You must be signed in to change notification settings - Fork 350
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
Allow a custom config class to be used via class_alias #112
Conversation
Allow a custom config class to be used via class_alias
This is a bad practice, and should not be done. The best thing to do here would be to resolve the config repository out of the ioc. |
I can't see this causing any issues however if you'd like to submit an alternative PR I'd be open to it |
It would 100% cause issues for people who have deleted all the facades aliases. |
Granted |
I'll send a pull... |
Cheers |
Actually, when are you doing a laravel 5 only version, because it would make a load of sense to use the config repository contract? |
#113 Should work on laravel 4 and laravel 5. |
* Revert VentureCraft#112 and follow VentureCraft#113 * Update RevisionableTrait.php * support Laravel 9 * Update readme.md remove misleading space (not being trimmed in model) * Bump dependencies for Laravel 10 * Update readme.md doc: userResponsible returns false and not null. --------- Co-authored-by: Lance Pioch <lancepioch@gmail.com> Co-authored-by: Reinier <reiniergombert@hotmail.com> Co-authored-by: Cristian Tabacitu <cristian.tabacitu@digitallyhappy.com> Co-authored-by: AHMAD BWIDANI <ahmad2135@gmail.com> Co-authored-by: Shift <shift@laravelshift.com> Co-authored-by: CedricFrossard <113982099+CedricFrossard@users.noreply.github.com>
From develop this time.