Skip to content
New issue

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

Compile Error - Declaration of Nette\SmartObject::__call #315

Closed
kropacekt opened this issue Jun 21, 2024 · 5 comments
Closed

Compile Error - Declaration of Nette\SmartObject::__call #315

kropacekt opened this issue Jun 21, 2024 · 5 comments

Comments

@kropacekt
Copy link

kropacekt commented Jun 21, 2024

Version: 4.0.4

Bug Description

Compile Error: Declaration of Nette\SmartObject::__call(string $name, array $args) must be compatible with Nette\Forms\Controls\BaseControl::__call(string $name, array $args): mixed in /var/www/html/vendor/nette/utils/src/SmartObject.php:28

Steps To Reproduce

Install:

  • nette/utils v4.0.4
  • nette/forms v3.2.3

Possible Solution

I suggest adding the mixed type to \Nette\SmartObject::__call or removing it from \Nette\Forms\Controls\BaseControl::__call.

Please let me know which solution you prefer, and I will create a pull request. Thank you.

@kropacekt kropacekt changed the title Compile Error - Declaration of Nette\SmartObject Compile Error - Declaration of Nette\SmartObject::__call Jun 21, 2024
@mabar
Copy link
Contributor

mabar commented Jun 21, 2024

Related issue (cz only) - https://forum.nette.org/cs/36492-compile-error-smartobject

@dg
Copy link
Member

dg commented Jun 21, 2024

Forms 3.0 are unsupported long time

@kropacekt
Copy link
Author

Forms 3.0 are unsupported long time

Sorry, I mentioned the wrong version. This error occurs in the latest version of nette/forms 3.2.3.

@kropacekt
Copy link
Author

@dg Now you can see?

Please let me know how can I help fix this error, thanks.

dg added a commit to nette/forms that referenced this issue Aug 8, 2024
@kropacekt
Copy link
Author

Hi @dg and thanks a lot for fixing this.

Would it be possible to release a new tag that includes this fix?

Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants