Allow non-Optional properties

[hkellaway]

Suggested by @Haud

[Haud]

Yes!

I've had time to take a deeper look into the code base. My thoughts are maybe there can be two operators: <~? for optional and <~! for non-optional. I think it's more immediately clear that way which operator does what, though I'm ok with <~~ and a non-optional type: <~~! or something.

I would also be more in favor of a init( json: JSON) as the protocol method than fromJSON, though I do understand its semantic equivalent in Encoder's toJSON

[hkellaway]

good suggestions! i'll keep you posted

[hkellaway]

the referenced PRs take your suggestions into account. non-optional properties are now allowed by using forceDecode_ functions or by using the <~~! operator. Additionally, I did like the idea of having to initialize with JSON, so the Decodable protocol was updated to reflect that.

you'll see these updates in 0.4.0 💥