cleaniquecoders / blueprint-macro Goto Github PK

Hi!

Today I was wondering why I repeat using

$table->unsignedInteger('user_id');
$table->foreign('user_id')->references('id')->on('users');

nested of using somthing like

$table->belongsTo('user');

Once I google "Laravel blueprint macro" your fresh package appear on the first search results :D

I like the developed features, and it seems that you still work on the documentation of the available features and macros.

I would like to contribute on this package if you have any further plan, and the first thing I think about is to use the same naming convention from Eloquent to deal with relations as I mention in my previous example. It will be more familiar for the developers to use "belongsTo" both in models and migrations for example.

I'm the first to watch the repo, and I hope to be the first to contribute based on your response and ideas

What about support nullable morph relation?

currently the community overcome this using

$table->string('parent_type')->nullable();
$table->integer('parent_id')->unsigned()->nullable();

$table->index(['parent_type', 'parent_id']);

we can support that using nullableMorphs macro?

As we use belongsTo from the standard Laravel Eloquent methods, I think we need to use timestamps nested of using boolean values:

for example addAcceptance must only use

$this->datetime($value . '_at')->nullable();

nested of using

$this->boolean('is_' . $value)->default(false);
$this->datetime($value . '_at')->nullable();

the is_ is just a computed prop that check if _at is null or not?

the same for expired marco?