This repository has been archived by the owner on Feb 18, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 48
Incorrect settable_type value upon migration #29
Comments
Unfortunately the merge request (Issue 21) has not solved my problem. I tried it on windows as well as on mac and still when i run php artisan settings:migrate the settable_type is inserted without backslashes like this: AppModelsUserUser Any advice please? Am I doing something wrong? Thanks! |
Same issue here. |
@divdax I had to create a fork until this gets fixed :) |
Can someone test this works on master? My old PC went to hell. |
Nah did not work after your last approved pull request. Still using my fork. |
@DarkGhostHunter Hey, can we do something about this? Should raise a PR? |
Pleas, hands full. |
Raised #35 for this one @DarkGhostHunter. Can you please take a look? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I am facing issue that when I run the php artisan settings:migrate command my database gets nicely seeded how ever the models do not include backslashes there for $user->settings does not work.
However I found out that if I run $user->settings()->initialize() it will recreate all of the settings with proper settable_type including backslashes. Here is a screenshot:
I am able to solve this issue by editing the fillSettings method in Pipes\CreateNewMetadata.php file like this:
However I am not sure if it is the proper approach.
Can someone please help me why is this behavior here?
The text was updated successfully, but these errors were encountered: