We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems like something has changed with Laravel 5.
Currently I'm not able to use a function name which is equal to the name of the property. So this is not working and I can't figure it out why
public function description() { return $this->description; }
This will throw an Undefined property: App\Presenter\ApplicationPresenter::$description
Undefined property: App\Presenter\ApplicationPresenter::$description
The only way I could get this to work is by using a different method name
public function getDescription() { return $this->description; }
or referencing the property like this
public function description() { return $this->entity->description; }
Am I doing something wrong or is this a bug in interaction with Laravel 5 ?
The text was updated successfully, but these errors were encountered:
Same problem here. Any updates?
Sorry, something went wrong.
Really appreciate this issue.
I also encountered this problem and I was wired until I see this.
I think, at least, it should be documented to make people be aware.
@pixelpeter Thanks for the $this->entity tip!!
$this->entity
No branches or pull requests
It seems like something has changed with Laravel 5.
Currently I'm not able to use a function name which is equal to the name of the property.
So this is not working and I can't figure it out why
This will throw an
Undefined property: App\Presenter\ApplicationPresenter::$description
The only way I could get this to work is by using a different method name
or referencing the property like this
Am I doing something wrong or is this a bug in interaction with Laravel 5 ?
The text was updated successfully, but these errors were encountered: