rappasoft / laravel-boilerplate

The Laravel Boilerplate Project - https://laravel-boilerplate.com
https://rappasoft.com
5.56k stars 1.58k forks source link

7.0 #1370

Closed rappasoft closed 4 years ago

rappasoft commented 4 years ago

So 7.0 is definitely far along now. It's still not at the point of release by any means.

This was a ground up rebuild, like seriously laravel new boilerplate.

I have been working on it almost 40 hours a week in my spare time since March. I've had so many setbacks and so many do overs, but I think I finally got the majority of the functionality down that I wanted. I did not TDD this project because I didn't know what I wanted to do, so there are currently no tests, but there will be.

The single biggest items left are:

Those are my big ticket items right now. Could you use this potentially for a new project, yeah. Would I recommend it? Not yet.

I'm calling on all tens of thousands of you who use this project as a daily driver to install 7.0 and beat the shit out of it for me. You can make PR's to that branch if you want, or if its small just drop it in here and i'll take care of it.

Keep in mind i'm constantly working on it so stuff will change as your testing.

Hope this is a welcomed update as i've been busting my ass on this for many months.

I did remove a lot of stuff from the current boilerplate for this version that I didn't see necessary anymore.

Cheers,

Anthony

P.S., these are some roadmap items:

Just to name a few.

bentran commented 4 years ago

Just wanted to say keep up the good work. I'm waiting for it to start a project.

PunchRockgroin commented 4 years ago

I'm curious about the idea of "App\Domains"... it looks like you are following the concepts here: https://stitcher.io/blog/laravel-beyond-crud-01-domain-oriented-laravel

Can you give a very brief overview of why you chose this vs putting Models/Controllers/etc in the usual locations? I'm sure this will help others who checkout the branch and see things elsewhere in the directory tree.

rappasoft commented 4 years ago

I definitely think it's a worthwhile approach for large applications. You'll know exactly where all the code is for each idea and it's organized. Plus it's easy to put back to the native Laravel way with the refactor tools that PHPStorm has.

Deceipt commented 4 years ago

I think it’s worth moving away from the crippling forms and making a component that implements this and can simply be specified with specific ones. Or use this package https://github.com/kdion4891/laravel-livewire-forms

rappasoft commented 4 years ago

What do you mean? I already have form helper components in the components/forms directory.

rappasoft commented 4 years ago

Decided to throw this one in: https://github.com/rappasoft/laravel-boilerplate/commit/d54e3933fda007de294be91d4b9b65a00f30dd2a

Deceipt commented 4 years ago

Yes it is, but the bottom line is why so many heaps of code? And reps? When you can simply implement 1 component and specify all these elements inside it. As you have now implemented work with tables, so do the forms. Just by writing 1 class and calling it, instead of sitting and writing a bunch of times the same tags and the same content

rappasoft commented 4 years ago

It would have been a good idea from the start, but i've been working on this for 6 months and there's no way i'm going to be redoing that much of it right now. Maybe the next version.

victoriusnet commented 4 years ago

@rappasoft I'm just wondering if a new main version of Laravel releasing, does it mean this boilerplate won't be easy to update? Just like now from 6 to 7 ?

rappasoft commented 4 years ago

Because the boilerplate is a project and not a package, there's no real upgrade guide. But definitely for the new version, it's a ground up rebuild. It will be for new projects.

PunchRockgroin commented 4 years ago

Any plans on a Log viewer, like before with https://github.com/ARCANEDEV/LogViewer?

rappasoft commented 4 years ago

There are many good log viewing plugins now, I'm leaving it up to the developer to choose their preference.

rappasoft commented 4 years ago

Tests are done, i'd consider it 99% if you're willing to keep the beta version of the livewire tables plugin.