-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading from a custom path works, however when I try to add a field the POST to /schematics/models/edit
#34
Comments
@cord Model creation was still focused on I solved this by adding a 'path' key to 'models' in the config. It will store models specified in the path there. You'll find this in
This is due to the fact that it's not (yet) supported to change columns order in migrations through the package. |
Just updated: Then trying this: leads to an error bar at the bottom "unprocessable entity" and the response still shows Btw. great package towards a nice roundtrip engineer tool! Currently, I use https://laravelsd.com and https://novapackages.com/packages/cloudstudio/resource-generator which have same nice details you might want to check. |
Hi @cord ! Could you maybe share how the class file looks like? Is it's path {app}/csm? I'm having trouble reproducing it. Are you perhaps on Windows as well? Thanks! Aim is to have a rocksolid tool at v1.0. Interesting shares, I'll look into them! |
looks like this - extended from a custom Model class
|
Ah, I see. There is no $fillable. I'll see what I can do about that this evening (since I'm at work right now). |
The issue is that you have not made the change in the ORM model to be fillable in the field where you're trying to insert the value to make this work add the following line
|
Reading from a custom path works, however when I try to add a field the POST to
/schematics/models/edit
fails with Exception
"message": "Cannot replace non-existing $fillable",
when hitting the save button.
Drag & drop to sort the new field does not work (can't drop in the list of existing fields)
Originally posted by @cord in #28 (comment)
The text was updated successfully, but these errors were encountered: