Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Impossible do define "null" value #79

Closed
mnapoli opened this issue Jun 19, 2013 · 7 comments
Closed

Impossible do define "null" value #79

mnapoli opened this issue Jun 19, 2013 · 7 comments
Assignees
Labels
Milestone

Comments

@mnapoli
Copy link
Member

mnapoli commented Jun 19, 2013

public function set($name, $value = null)

Impossible to define explicitly a null value:

$container->set('service', null);

because:

if null, returns a ClassDefinitionHelper

so it will create a ClassDefinition for the entry name ("service" in the example).


One solution would be to check the numbers of arguments given: if $value was given and specified explicitly to null, then we define a null value.

Another would be to return a more generic helper that would allow:

$container->set('service')->value(null);

but that seems complex because of how it currently works with the ClassDefinitionHelper.

Finally, by adding a NullValue class:

$container->set('service', new NullValue());
@ghost ghost assigned mnapoli Jun 19, 2013
mnapoli added a commit that referenced this issue Jun 23, 2013
@mnapoli
Copy link
Member Author

mnapoli commented Jun 23, 2013

Fixed.

// Will set a null value
$container->set('foo', null);

// Will return a ClassDefinitionHelper for inline definition
$container->set('foo')->addParameter(/* ... */);

As a consequence:

// Will not do anything as such
$container->set('foo');

// Will throw an exception (because set returns null)
$container->set('foo', null)->addParameter(/* ... */);

@mnapoli mnapoli closed this as completed Jun 23, 2013
@dsummersl
Copy link

How does this work in YAML? I have tried variations of:

My\Implementation:
  constructor:
    param: null

and

My\Implementation:
  constructor:
    param: NullParam

and

nullparam: null
My\Implementation:
  constructor:
    param: nullparam

@mnapoli
Copy link
Member Author

mnapoli commented Aug 6, 2013

In the YAML definitions, parameters are always references to other entries, so as you guessed:

My\Implementation:
  constructor:
    param: null

will look for an entry for the name "null" in the container.


I just learned that YAML supports null value, and in different forms. Apparently, you can use any of this:

nullparam: null
nullparam: ~
nullparam:

(see also http://yaml.org/type/null.html or symfony/symfony#7274)

The question now is: does PHP-DI supports it on its end. I must confess I haven't tried it, and there are no tests for this. Given your last suggestion is valid YAML, if you have tried it and it doesn't work, then it's a bug.

Could you confirm that any of the 3 solutions above don't work?

@dsummersl
Copy link

I tried all three. I get the following exception in all three cases:

ReflectionException: Class nullparam does not exist in /opt/site/vendor/mnapoli/php-di/src/DI/Factory.php on line 48

@mnapoli
Copy link
Member Author

mnapoli commented Aug 7, 2013

Thanks, I have created a new issue for this: #95

@dsummersl
Copy link

Thanks! If this is something that you dno't have time for I can also devote a little time to debugging this today...

@mnapoli
Copy link
Member Author

mnapoli commented Aug 7, 2013

thanks, feel free to submit a pull request. If you have time only to write tests to reproduce it that's good too. FYI I may not have a lot of time to look at it in the next days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants