Throw when xxxOptions are null #1076
We rely on the following pattern throughout the codebase.
Let's change this to the following one
The table below represents the impact of the proposed change.
I agree about the API code contract breakage. However, now is the time for this (hence the stabilization label). v0.22 is taking quite a long time to get out of the woods as we're trying to obsolete as many things as possible in order to be able to release v1.0 as the next version after it.
Regarding the additional code verbosity, I'm not sure to see what you refers to. Could you please elaborate further on this topic? Maybe with an example?
From another standpoint, I'm not sure I see the added value of allowing