Fix #1424: Set value for boolean field without default value

[chrfritsch]

Summary
This fixes a validation issue for boolean fields without any default value for new posts.

Test plan

1. Define a field like this in config.yml:

-
  label: Awesome
  name: awesome
  widget: boolean

1. Create a new item in the collection
2. Try to publish the item

You'll get an "AWESOME IS REQUIRED" error.

For the record, specifying default: false for the field makes the problem disappear.

A picture of a cute animal (not mandatory but encouraged)

[barthc]

@chrfritsch could you add a simple test to confirm this behavior in the entries.spec file

[chrfritsch]

Maybe something like this? It's my first jest test I ever wrote :D I don't understand why it returns an object with title: false. Maybe there is something else broken? But without the fix the object was empty.

[barthc]

boolean widgets don't have fields attrs, test for { name: 'boolean', widget: 'boolean' } for example, which should output { boolean: false }

[chrfritsch]

I switched the parent back to object, like all the other tests. That was a leftover from some back and forth testing...

[erquhart]

We really want to avoid hardcoding widget names. The underlying issue here is bigger than just the boolean widget.

[erquhart]

Thanks for this @chrfritsch! I'm not sure it's the right approach, though. What we really need is for widgets to set their own default values. There's some discussion around this in #1407, but it isn't fully fleshed out yet.

Going to close this, but please comment if you have any thoughts on it or questions!