require on directives should pass null when the controller is not found and is optional

[kentcdodds]

Currently it's passing undefined when it should pass null. Identified in #9392.

I'm working on updating the #9392 PR to include this fix.

[caitp]

I don't know if a new issue is needed for this, I'm not sure if anyone even agrees with me that not being null is a bug --- I think it would be better, but who knows

[kentcdodds]

Yeah, I like the idea of commits being related to an issue, that's why I created the issue in the first place.

[btford]

null seems a bit better, but I don't think that there's a strong enough argument to warrant changing the behavior :/

[kentcdodds]

Understood. It's definitely a breaking change, although it's much smaller than many others going into 1.3...

[caitp]

I'm pro-changing it, since we explicitly set it to null in the non-array case. It's good to be consistent

[caitp]

And as for it being a breaking change, I don't think anyone is realistically depending on it being undefined

[kentcdodds]

@caitp, I concur with that analysis of the breaking-ness of this change :-)