fix Getting unknown property

[sichkarev]

Q	A
Is bugfix?	✔️
New feature?	❌
Breaks BC?	❌
Fixed issues

[machour]

This doesn't look right to me. If you're misconfigured the behavior, the application should throw, and you should fix your code, instead of silently getting a null.

What's your use-case here?

[sichkarev]

What's your use-case here?

In our project, we use ActiveRecords in migrations. Data are received from database and after receiving, properties of model will be casted to any types.
('typecastAfterFind' => true)

After switching to PHP 8.3, this behavior began to generate an exception, because The model describes properties that do not yet exist (they will be created in one of next migrations).

public function behaviors(): array
    {
        return ArrayHelper::merge(
            parent::behaviors(),
            [
                'typecast' => [
                    'class' => AttributeTypecastBehavior::class,
                    'attributeTypes' => [
                        'attribute_example' => AttributeTypecastBehavior::TYPE_INTEGER,
                    ],
                    'typecastBeforeSave' => true,
                    'typecastAfterFind' => true,
                ],
            ]
        );
    }

Example code in first migration:

$countries = Country::find()->all();

Example code in second migration:

        $this->addColumn('countries', 'attribute_example', $this->integer());

[sichkarev]

instead of silently getting a null.

Even before my commit, the class was returning null

I just added a simple check for suppress the exception