Converting existing model to Smart model

[deiucanta]

Let's say you have the user model already. The migration is there and the database is up to date. You want to use Smart model from now on.

Converting the model will generate a new migration as if nothing was in the database. This happens because we didn't track previous states of the user model.

If we add a command that doesn't generate a new migration but updates the smart.json file, I think we should be good on this issue.

Am I missing anything?

[robsontenorio]

I consider this can messup things , because is dangerous.

I do prefer convert the project into smart models, delete all migrations file and generate then again with Smart.

[deiucanta]

@robsontenorio I know you are converting an existing project to use this package. Let us know how it goes.

Meanwhile, a few questions

• how will you handle the migrations that are generated by 3rd party packages (laravel cache table, queue failed jobs table, password resets table)?
• when you create a new laravel project you get 2 migrations by default (users and password_resets if I'm not mistaken) - do you delete them and recreate them via smart models?

---

There are two cases we need to support

• existing migrations with app models
• existing migrations from external packages

[robsontenorio]

Just finished the project migration. It took about 1h with 25 models.

• Modify models to extends from Smart Models, except User model. Because it already extends Authenticate model.
• Keep all 3rd party migrations, including user Model.
• Drop all another app migrations
• php artisan smart:migration

The process was smooth due to app automatic tests.

[deiucanta]

@robsontenorio 1h is pretty good!

• did you feel the API is lacking fluency beside the timestamps fields?
• are you fine leaving the User model as is?
• is it a REST API or a full-stack app?

[robsontenorio]

• Yes, I miss short handy timestamp() statement.
• Yes, I dont touch User model. For now, i don`t have a solution.
• Laravel REST API only