Dangerous to define variables in traits that are supposed to be overridden in child classes?

[kjostling]

Public $timestamps = false is used to disable timestamps in model implementations, however doing this triggers a warning in PhpStorm that is related to this restriction in PHP.
https://www.php.net/traits#language.oop5.interfaces.examples.ex1

We avoid the fatal error in Laravel by having the Model as an abstract class inbetween the implementation and the trait, but that "feels" like a risky workaround that is not supposed to work.

What do you think about this?

Files:
https://github.com/laravel/framework/blob/8.x/src/Illuminate/Database/Eloquent/Model.php
https://github.com/laravel/framework/blob/8.x/src/Illuminate/Database/Eloquent/Concerns/HasTimestamps.php