[Idea] Make attributes nullable by default

[tabacitu]

Ok, so it's just an idea - don't know if even I agree with it yet :-))

I think it would be faster for attributes to default to nullable, since that's how most attributes are, usually. I personally don't like to enforce more restrictions than necessary. So if I make a mistake and forget to make an attribute nullable, I have to go back, change the migration, change the request, run migrate fresh and everything. Such a drag. Having attributes non-nullable would be faster to develop, imho.

However, I'm aware that Laravel itself makes attributes nullable by default in migrations. You have to specify to make them nullable. So it might make perfect sense for the generator to follow the same pattern.

What do you think?

[tswonke]

In our projects we can't really say whether there are more nullable fields - or not.
We wouldn't make that default, but we could add a config/env for that

[tabacitu]

Config value sounds great! Will post here when I start working on it.