You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current generated ContentBehavior does not use DateTime; but generates
/** * @var DateTime|null Value for field with the handle “startDate”. */public$startDate;
so the class DateTime cannot be resolved. Would you mind changing that, you only have to include the slash as you do it for other classes
/** * @var \craft\elements\db\UserQuery Value for field with the handle “user”. */public$user;
I know the next thing actually belongs to a separate issue and is not related to the ContentBehavior, but to the ElementQueryBehavior but I'll mention it anyway. It has the properties
* @method self headline(mixed $value) Sets the [[headline]] property
So when I do
Entry::find()->headline('foo')->all();
PHPStorm cannot resolve all because the behavior does not have such a method.
This can be fixed via
* @method \craft\elements\db\ElementQuery headline(mixed $value) Sets the [[headline]] property
So PHPStorm knows at least an ElementQuery is returned. Same goes for the new "merged" CustomFieldsBehavior
The text was updated successfully, but these errors were encountered:
Craft 3.4.9 is out now with the fix for this. Note that you will need to delete your current CustomFieldBehavior.php file before the change will take effect.
Description
The current generated
ContentBehavior
does notuse DateTime;
but generatesso the class
DateTime
cannot be resolved. Would you mind changing that, you only have to include the slash as you do it for other classesI know the next thing actually belongs to a separate issue and is not related to the ContentBehavior, but to the
ElementQueryBehavior
but I'll mention it anyway. It has the propertiesSo when I do
PHPStorm cannot resolve
all
because the behavior does not have such a method.This can be fixed via
So PHPStorm knows at least an ElementQuery is returned. Same goes for the new "merged" CustomFieldsBehavior
The text was updated successfully, but these errors were encountered: