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
In general this is a bad idea because some functions that call language constructs like isset() on an instance will fail to return true when __get() would still return a valid item. See #2205 for one example.
Unless there's some compelling reason not to, I propose each of these classes should have a basic __isset() added, modeled after their __get(). E.g.:
public function __isset($name)
{
return isset($this->attributes[$name]);
}
The text was updated successfully, but these errors were encountered:
The following classes have a magic
__get()
method without a corresponding__isset()
:In general this is a bad idea because some functions that call language constructs like
isset()
on an instance will fail to returntrue
when__get()
would still return a valid item. See #2205 for one example.Unless there's some compelling reason not to, I propose each of these classes should have a basic
__isset()
added, modeled after their__get()
. E.g.:The text was updated successfully, but these errors were encountered: