FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Add return type declarations to future-proof vs Symfony\Component\Form\FormTypeInterface::getParent() by ywarnier · Pull Request #8 · krixer/OhGoogleMapFormTypeBundle · GitHub

Add return type declarations to future-proof vs Symfony\Component\Form\FormTypeInterface::getParent() - #8

Open
ywarnier wants to merge 1 commit into
krixer:masterfrom
ywarnier:patch-1
Open

Add return type declarations to future-proof vs Symfony\Component\Form\FormTypeInterface::getParent()#8
ywarnier wants to merge 1 commit into
krixer:masterfrom
ywarnier:patch-1

Conversation

ywarnier commented Feb 8, 2024

Copy link
Copy Markdown

Symfony 5.4 warns of
Method "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Oh\GoogleMapFormTypeBundle\Form\Type\GoogleMapType" now to avoid errors or add an explicit @return annotation to suppress this message.

This change has not been tested in all necessary contexts but it seems relatively straightforward.

…m\FormTypeInterface::getParent()

Symfony 5.4 warns of 
Method  "Symfony\Component\Form\FormTypeInterface::getParent()" might add "?string" as a native return type declaration in the future. Do the same in implementation "Oh\GoogleMapFormTypeBundle\Form\Type\GoogleMapType" now to avoid errors or add an explicit @return annotation to suppress this message.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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

Successfully merging this pull request may close these issues.

1 participant


Back | FazBrowse Home | New Git URL