We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Just a suggestion, but Laravel's conventions are generally put(), get(), has(), all().
Would it make more sense, from a Laravel point of view, but use these names?
Theme::getThemes(); becomes Theme:all() Theme::themeExists('theme-namespace'); becomes Theme::has('theme-namespace');
Other than that, terrific job, can't wait to use this!
The text was updated successfully, but these errors were encountered:
Renamed method names #1
fc9c3f3
karlomikus
No branches or pull requests
Just a suggestion, but Laravel's conventions are generally put(), get(), has(), all().
Would it make more sense, from a Laravel point of view, but use these names?
Theme::getThemes(); becomes Theme:all()
Theme::themeExists('theme-namespace'); becomes Theme::has('theme-namespace');
Other than that, terrific job, can't wait to use this!
The text was updated successfully, but these errors were encountered: