search

pqrs / l5b-crud

CRUD artisan command for rappasoft/laravel-5-boilerplate
21 stars 15 forks source link

Feature Request: events/listeners and frontend generation #6

Open waltermaldonado opened 5 years ago

waltermaldonado commented 5 years ago

First of all, congratulations, this is quite awesome, I'm sure I'll use it!

Am I missing something or you forgot about the events and listeners? Also how would I do to generate the files in Frontend?

Thank you very much!

pqrs commented 5 years ago

This package does nothing in the Frontend. I think the needs there can be so different than it won't be really useful. However, in the backend and with a boilerplate like rappasoft's is where you can save lots of time because everything is more uniform.

About events and listeners, I thought about it but to be honest I completely forgot it. I put in my to do list.

Thanks to you for your comments, they are much appreciated.

pqrs commented 5 years ago

Hi again @waltermaldonado, I have just released 1.3.7 version with Events and Listeners for Create, Update and Delete methods. Still thinking if I should add two more events for recovering and permanently deleting. What do you think?

rabol commented 5 years ago

I actually also think it would be a good idea if the basics was created for the front end like controller, events, requests

That would also save a lot of time

pqrs commented 5 years ago

Hi again @rabol.... maybe just the basics as you are pointing is something to consider, I'm thinking about model, attributes, controller, repositories and requests, and leaving routes, breadcrumbs and views. Let me think about it, I'll try to do it after your lang file suggestion.

Thanks again for your comments.

waltermaldonado commented 5 years ago

Hi again @waltermaldonado, I have just released 1.3.7 version with Events and Listeners for Create, Update and Delete methods. Still thinking if I should add two more events for recovering and permanently deleting. What do you think?

I am not so sure if it is so usual in CRUD. Maybe it would be good to have this option, but with a secondary importance.

Hi again @rabol.... maybe just the basics as you are pointing is something to consider, I'm thinking about model, attributes, controller, repositories and requests, and leaving routes, breadcrumbs and views. Let me think about it, I'll try to do it after your lang file suggestion.

Thanks again for your comments.

That would be perfect in my opinion, since the last tree you pointed out are very specific.