-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Removed deprecated stuff from the Config component #14927
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
Conversation
dosten
commented
Jun 9, 2015
Q | A |
---|---|
Bug fix? | no |
New feature? | no |
BC breaks? | yes |
Deprecations? | no |
Tests pass? | yes |
License | MIT |
// as some some loaders do not call the parent __construct() | ||
// @deprecated should be removed in 3.0 | ||
$locator = $loader->getLocator() ?: $this->locator; | ||
$locator = $loader->getLocator(); | ||
$resource = $locator->locate($resource, $this->currentDir, false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't that introduce a possible failure? As apparently not all $loader->getLocator()
returned something (otherwise the fallback would have never been called), this may now fail as $locator
can be empty?
Or was this changed in $loader->getLocator()
, so that it always returns a locator?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, not calling the parent constructor to initialize the locator in classes extending FileLoader is not supported anymore in 3.0. the object should be built in a working state.
Btw, it looks like we are missing a deprecation warning here to warn about that in 2.x versions. This should be added before removing deprecated stuff from 3.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In which branch the deprecation warning should be added? 2.8?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2.7 IMO
This PR is ready to be merged. |
👍 |
Thank you @dosten. |
…sten) This PR was merged into the 3.0-dev branch. Discussion ---------- Removed deprecated stuff from the Config component | Q | A | ------------- | --- | Bug fix? | no | New feature? | no | BC breaks? | yes | Deprecations? | no | Tests pass? | yes | License | MIT Commits ------- 07a1790 Removed deprecated stuff from the Config component