Required but nullable arguments should be required to be specified in the config

[ondrejmirtes]

Let's say we have a constructor that looks like this:

	public function __construct(
		private ?string $singleReflectionFile
	)

And we have a service config that looks like this:

	-
		class: Foo

In this case nette/di will autowire the null value into this constructor parameter. But the the constructor parameter is required for a reason - I want the user to specify it. Omitting it is dangerous because the library can't assume that the user wants null in there, because they might not even know that I want them to specify the value. I want the user to explicitly pass a value.

I realize this is a big BC break, but maybe the behaviour could be opt-in with some feature toggle before making it mandatory in the next major version.

[dg]

That makes sense. I'll try to add a deprecation notice for this situation in version 3.1, which should just warn about the changes in 4.0.

[ondrejmirtes]

Awesome, thank you!

[dg]

I wonder if it shouldn't work that way for objects too? Ie. __construct(private ?Foo $foo)

[ondrejmirtes]

Yeah, if Foo couldn't be autowired, it shouldn't silently pass null in there.