Feature Request: softDeletes Support

[EHLOVader]

This would be a nice to have. Appears that it would require additional work model side though.

I don't know if that would work.

[andreluizmorita]

#58

[tabacitu]

@EHLOVader are you still using this package, and want it to support SoftDeletes? I now have write access and would love SoftDeletes too.

I know Jeffrey passed on it, but it was probably due to him not wanting to maintain it, rather than feeling it's not a good idea. If we have a good PR for it, I think it's very much worth including in v2 #170. The package is finally getting the love it needs - no better time to work on this feature than now 😄

Let me know if you are able to help with this, I'd love to have SoftDeletes support in v2.

Cheers!

[eightyfive]

I think this feature should include all possible special column types.

These are the types that don't specify a column name:

$table->timestamps();
$table->rememberToken();
$table->softDeletes();
// ...

So they would be pretty easy to identify in SchemaParser:: parseSegments.

Validation should use something like method_exists(Blueprint::class, $field[0]), not checking for names.

I can have a go at it. Let me know.

PS: Is there already some kind of validation of all columns types in place?

[tabacitu]

Please take a stab at it, if you can, @eightyfive . Personally I see it as a flag, rather than the previous implementation. Something like:

php artisan make:migration:schema create_groups_table --schema="name:string:unique,description:string" --softDeletes

[eightyfive]

Hi,

I took a different approch in another package:
https://github.com/eightyfive/laravel-exodus/blob/master/src/Exodus.php#L118

I basically allow any "special" column types: id(), rememberToken(), timestamps(), softDeletes(), etc...

Let me know @tabacitu if this is something you would like to see implemented in the generators.

Cheers.