8000 Fix bug when using an private aliased factory service by wouterj · Pull Request #17942 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

Fix bug when using an private aliased factory service #17942

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

Closed
wants to merge 2 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Fix bug when using an private aliased factory service
  • Loading branch information
wouterj committed Feb 27, 2016
commit 5a995bd97efc231ead0b6cc94e040d49c535ff94
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,6 @@ private function updateFactoryServiceReference($factoryService, $currentId, $new
return;
}

return $currentId === $factoryService ? $newId : $currentId;
return $currentId === $factoryService ? $newId : $factoryService;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$currentId is the current ID of the removed alias, while $factoryService is the original ID of the factory service.

If the factory service equals the ID of the removed alias, it should be updated to become the actual service ID. However, if the factory service does not equal the ID of the removed alias, the original value should be used.

With the old code, it was always replacing the original code, either with the actual definition ID or the ID of the removed alias (which was causing the troubles people were reporting).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch @wouterj 👏

}
}
0