-
-
Notifications
You must be signed in to change notification settings - Fork 90
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
Prepare major release #609
Conversation
0aa95b4
to
0af359f
Compare
If we follow the same strategy than other bundle, we should also
And we might determine what we do with #600 (review) |
596d228
to
9929d6a
Compare
Done
We can still implement the feature on the next major version |
5e0c2d0
to
1aa5c38
Compare
$containerConfigurator->services() | ||
|
||
->set('sonata.seo.page.default', '%sonata.seo.page.default.class%') | ||
->set('sonata.seo.page.default', SeoPage::class) | ||
->public() |
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.
I haven't checked the usages, but do we need services to be public?
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.
Not sure if symfony still recommends using the service container. If it's deprecated we could make this private.
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.
Looks like it depends on the usage:
In addition, services not meant to be used by the application directly, should be defined as private. For public services, aliases should be created from the interface/class to the service id.
(I haven checked, but I guess they don't recommend using the service container directly.)
74f9b04
to
8d5a296
Compare
$connectionIterator = new Definition('%sonata.seo.exporter.database_source_iterator.class%', [ | ||
$connectionIterator = new Definition(DoctrineDBALConnectionSourceIterator::class, [ |
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.
I'm not familiar with this, but if we have paramteter here should not be better to keep it and set it in config?
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.
We could improve this by allowing a custom service via the config, but for now we should get rid of all class parameters.
@@ -86,7 +89,7 @@ private function configureSitemap(array $config, ContainerBuilder $container): v | |||
// define the sitemap proxy iterator | |||
$sitemapIteratorId = 'sonata.seo.source.doctrine_sitemap_iterator_'.$pos; | |||
|
|||
$sitemapIterator = new Definition('%sonata.seo.exporter.sitemap_source_iterator.class%', [ | |||
$sitemapIterator = new Definition(SymfonySitemapSourceIterator::class, [ |
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.
I'm not familiar with this, but if we have paramteter here should not be better to keep it and set it in config?
Before next major release we should decide about one importan thing. After 2 months (59 days) support for PHP 7.3 will be end. If we drop it now then we can also declare types for parameters. Do it in stable branch will be BC. WDYT? @sonata-project/contributors |
It's already dropped in this bundle: Line 23 in 23cf25d
|
I want check it this bundle before major release in the evening. So can we wait with major release to tomorrow? |
We should try with an alpha/beta version anyway |
Subject
I am targeting this branch, because this should be the last changes for the next major release.
Changelog