search

laravel / blog-contest-may-mayhem

242 stars 16 forks source link

Make Laravel Fluent Again with SmartFields 🔥 #61

Open deiucanta opened 6 years ago

deiucanta commented 6 years ago

https://medium.com/@deiucanta/make-laravel-fluent-again-with-smartfields-7d543e725365

castroalves commented 6 years ago

Nice post. But lobby for votes is against the rules, buddy. See here.

deiucanta commented 6 years ago

@castroalves I thought it's about lobbying on social media. Am I wrong?

To be fair to those with smaller audiences, you may not lobby for votes via Twitter, etc.

castroalves commented 6 years ago

@deiucanta I think you can't lobby anywhere. @taylorotwell is the best person to help with it.

deiucanta commented 6 years ago

@castroalves I just removed the link to the contest from my blog post, just to be on the safe side :)

castroalves commented 6 years ago

@deiucanta totally agree 👍

minthemiddle commented 6 years ago

@deiucanta Interesting proposal. I share the pain and am curious what some seasoned core contributors think about it.

deiucanta commented 6 years ago

@minthemiddle Thanks for the feedback! This is something that goes beyond the blog contest and I'm curious as well what they think about it.

@taylorotwell @themsaid @barryvdh @adamwathan @GrahamCampbell

mnapoli commented 6 years ago

I think the same problem will apply to #57, even though they don't have a direct link to the issue the article is about the contest so… it attracts people here. Tricky to set the limit though! ^^

laraning commented 6 years ago

I like the idea. We can then generate a migration directly from the model class.

The issue might be with versioning. Like if you, on a 2nd migration, need to change the fields... how would the migration know what to change given the first model fields structure that were defined earlier.

amaelftah commented 6 years ago

@laraning django framework makes the same idea , it generates the migrations from the model class , and if any changes happened on the model class , then we must execute this command in order to create a new migration with the changes

so i think if there's some sort of artisan command that reads the fields from model , and compare them to current database table columns , then generate migrations with only the changes , it would solve the problem , but not sure if there's a better solution .