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

The parameter and property types are not correctly returned when they are nullable #153

Open
jenky opened this issue Jan 27, 2024 · 9 comments

Comments

@jenky
Copy link

jenky commented Jan 27, 2024

Version: 4.1.3

Bug Description

getType does not return correct type

Steps To Reproduce

$class = new ClassType('Hello');

$method = $class->addMethod('greeting');

$param = $method->addParameter('name', null)
    ->setType('string')
    ->setNullable();

echo $param->getType(); // "string"

The class was generated correctly

class Hello
{
        public function greeting(?string $name = null)
        {
        }
}

Expected Behavior

$param->getType() should return ?string or null|string instead of string

@kosciuk
Copy link

kosciuk commented Jan 27, 2024

For me is ok, if you set null with setNullable, you should check with:

echo $param->isNullable(); // true

@jenky
Copy link
Author

jenky commented Jan 27, 2024

Why do I need to check isNullable when I already know it by using setNullable? I want to get the correct param type not the nullable state.

@kosciuk
Copy link

kosciuk commented Jan 27, 2024

Why do you ask for the type if you already know that the answer is string? In large programs you won't know where the type is set or what type it is.

Example: I generate code with ->setType[$entity->getPhpType()].

@jenky
Copy link
Author

jenky commented Jan 27, 2024

Why do you ask for the type if you already know that the answer is string?

It's just an example to reproduce the bug

In large programs you won't know where the type is set or what type it is.

Example: I generate code with ->setType[$entity->getPhpType()].

So what is your point then?. Your example is clearly the reason getType should return the correct types

@kosciuk
Copy link

kosciuk commented Jan 27, 2024

I am a user, I do not participate in the development, I think it is correct to check with isNullable, otherwise you have to parse the response to know if it is nullable or string

@jenky
Copy link
Author

jenky commented Jan 27, 2024

isNullable doesn't return true in the case of ->setType('null|string') but it does return true for ->setType('?string').

If you take a look at this Nette\Utils\Type::fromString

public static function fromString(string $type): self
{
    // ...

    if ($type[0] === '?') {
	return new self([substr($type, 1), 'null']);
    }

    // ...
}

It is clear that the fromString method is capable of parsing and returning the correct types. When using Nette\Utils\Type::fromString('?string'), it correctly returns the expected types. However ->setType('?string')->getType() doesn't (which uses Nette\Utils\Type::fromString behind the scenes). With all the inconsistencies, I believe this is a bug.

Anyway, let the repository owner decide on further actions regarding this report.

@dg
Copy link
Member

dg commented Feb 8, 2024

This behavior is for historical reasons, because functions were created at a time when union types like null|string didn't even exist yet. I would like to change this, but it will break compatibility.

@sovetski
Copy link

+1 for this

@dg it can be included in a major version maybe?

@dg
Copy link
Member

dg commented Sep 10, 2024

@sovetski yes

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

No branches or pull requests

4 participants