Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

[DependencyInjection] Fix YAML example in "Defining a Service Locator" section#16458

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
javiereguiluz merged 1 commit intosymfony:4.4fromjbieliauskas:patch-2
Feb 4, 2022

Conversation

jbieliauskas
Copy link
Contributor

Using this example inv5.3.13 gives this error:

Symfony\Component\DependencyInjection\Definition::setArguments(): Argument #1 ($arguments) must be of type array, Symfony\Component\DependencyInjection\Argument\ServiceLocatorArgument given, called in /project/vendor/symfony/dependency-injection/Loader/YamlFileLoader.php on line 527

I assume this is because!service_locator is the first constructor argument but it's passed as an array of constructor arguments, in which case the example is not right.

Service locator is a first constructor argument but is passed as an array of constructor arguments.
@carsonbotcarsonbot added this to the4.4 milestoneJan 30, 2022
@carsonbotcarsonbot changed the titleFix YAML example in "Defining a Service Locator" section[DependencyInjection] Fix YAML example in "Defining a Service Locator" sectionFeb 4, 2022
@javiereguiluz
Copy link
Member

Good catch Justas! Thanks and congrats on your first Symfony Docs contribution 🎉

@javiereguiluzjaviereguiluz merged commitcc7a726 intosymfony:4.4Feb 4, 2022
@jbieliauskas
Copy link
ContributorAuthor

@javiereguiluz Will this change be applied to other versions like 5.x, 6.x?

@jbieliauskasjbieliauskas deleted the patch-2 branchFebruary 5, 2022 20:37
@javiereguiluz
Copy link
Member

javiereguiluz commentedFeb 5, 2022•
edited
Loading

Yes, it should be already in all upper and maintained branches. We "upmerge" all Pull Requests. Cheers!

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Projects
None yet
Milestone
4.4
Development

Successfully merging this pull request may close these issues.

3 participants
@jbieliauskas@javiereguiluz@carsonbot
[8]ページ先頭
©2009-2025 Movatter.jp