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
Hello, at my company we're trying to use Laravel Excel but we still have issue on IMPORTS (not exports), where a 0 value is actually considered as NULL when it shouldn't be.
We use validation rules such as : $rules['Some_Column'] = 'required_unless:Some_Column,null|nullable|string'
With the 0 values, we can't properly validate our data, we want the value 0 to be considered as a 0 and not a null. Implementing the trait WithStrictNullComparison only applies to exports as far as I understood it, so it doesn't help our case. I found an old closed ticked on this matter but no real solution to get around this issue, any idea?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, at my company we're trying to use Laravel Excel but we still have issue on IMPORTS (not exports), where a 0 value is actually considered as NULL when it shouldn't be.
We use validation rules such as :
$rules['Some_Column'] = 'required_unless:Some_Column,null|nullable|string'
With the 0 values, we can't properly validate our data, we want the value 0 to be considered as a 0 and not a null. Implementing the trait WithStrictNullComparison only applies to exports as far as I understood it, so it doesn't help our case. I found an old closed ticked on this matter but no real solution to get around this issue, any idea?
Beta Was this translation helpful? Give feedback.
All reactions