We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm getting this error when I try to pass an array to a model property that is cast as json.
The generator made the entire class by itself, and those are the field generated stuff:
/* * @property array $extra_fields */ protected $casts = [ 'extra_fields' => 'json' ];
Exception:
The tool created the model adding this use clause:
use Reliese\Database\Eloquent\Model as Eloquent;
When I switched it to the Illuminate class, it worked.
use Illuminate\Database\Eloquent\Model as Eloquent;
Can this be fixed or is there a way to use Illuminate classes instead of classes from the Reliese namespace?
The text was updated successfully, but these errors were encountered:
Sure, you can use Illuminate\Database\Eloquent\Model as the default parent class. You just need to change it in the config file (https://github.com/reliese/laravel/blob/master/config/models.php#L55)
Illuminate\Database\Eloquent\Model
Sorry, something went wrong.
Oh I see, I did not notice that one. Thanks for the reply. I'll update my code first thing tomorrow. Thank you!
No branches or pull requests
I'm getting this error when I try to pass an array to a model property that is cast as json.
The generator made the entire class by itself, and those are the field generated stuff:
Exception:
The tool created the model adding this use clause:
use Reliese\Database\Eloquent\Model as Eloquent;
When I switched it to the Illuminate class, it worked.
use Illuminate\Database\Eloquent\Model as Eloquent;
Can this be fixed or is there a way to use Illuminate classes instead of classes from the Reliese namespace?
The text was updated successfully, but these errors were encountered: