You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I create a model and table in DevTools that contains a nullable field, and when I open the create form in CRUD, I get the default value "NULL" as a "STRING" instead of an empty field.
What I expected to happen
I expect the input to be empty (value='').
What happened
I am getting the value NULL as a string (value='NULL').
What I've already tried to fix it
We have a datetime field in the database that is nullable. When I went to create, the datepicker didn't work—it didn't show up at all until I set ->value('') to empty in the datetime_picker. That's how we solved the issue of getting the datepicker to work, because if "null" stays as a string, it throws an error since it can't parse the date (Uncaught TypeError: defaultDate() Could not parse date parameter: NaN). However, it's not right that we have to manually remove the string "null" from every input field that is nullable in the database.
Is it a bug in the latest version of Backpack?
After I run composer update backpack/crud the bug... is it still there? YES
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
Hello there! Thanks for opening your first issue on this repo!
Just a heads-up: Here at Backpack we use GitHub Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.
Long questions (I have done X and Y and it won't do Z wtf) - Stackoverflow, using the backpack-for-laravel tag;
Showing off something you've made, asking for opinion on Backpack/Laravel matters - Reddit;
Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.
Bug report
What I did
I create a model and table in DevTools that contains a nullable field, and when I open the create form in CRUD, I get the default value "NULL" as a "STRING" instead of an empty field.
What I expected to happen
I expect the input to be empty (value='').
What happened
I am getting the value NULL as a string (value='NULL').
What I've already tried to fix it
We have a
datetime
field in the database that is nullable. When I went to create, the datepicker didn't work—it didn't show up at all until I set->value('')
to empty in thedatetime_picker
. That's how we solved the issue of getting the datepicker to work, because if "null" stays as a string, it throws an error since it can't parse the date (Uncaught TypeError: defaultDate() Could not parse date parameter: NaN
). However, it's not right that we have to manually remove the string "null" from every input field that is nullable in the database.Is it a bug in the latest version of Backpack?
After I run
composer update backpack/crud
the bug... is it still there? YESBackpack, Laravel, PHP, DB version
When I run
php artisan backpack:version
the output is:The text was updated successfully, but these errors were encountered: