Symfony 3.4 dont set arguments when i configure it in yaml service config












0















i use Symfony 3.4 and i try to migrate an Silex Application to it. So i cant use the autowiring of Symfony.



My service.yml looks like



services:
# default configuration for services in *this* file
_defaults:
# automatically injects dependencies in your services
autowire: false
# automatically registers your services as commands, event subscribers, etc.
autoconfigure: false
# this means you cannot fetch services directly from the container via $container->get()
# if you need to do this, you can override this setting on individual services
public: false

audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- method: 'addPersister'
argument:
- '@audit.persister_elasticsearch'


The compiled cach class looks like:



$this->services['audit.persister.base'] = $instance = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister();

$instance->addPersister();


An i got the error:



 Type error: Too few arguments to function MyBundleSecurityAuditPersisterChainedEntityTrailPersister::addPersister(), 0 passed in /var/www/html/api/var/cache/local/ContainerAdjsiif/getAudit_Persister_BaseService.php on line 14 and exactly 1 expected


The error is correct. Because the cached class creator does not provide the argument that i have set in config.



Anyone an idea why the argument will not set in generated cache?










share|improve this question























  • Hint: Cache is cleared.

    – RalfGe
    Nov 22 '18 at 9:22
















0















i use Symfony 3.4 and i try to migrate an Silex Application to it. So i cant use the autowiring of Symfony.



My service.yml looks like



services:
# default configuration for services in *this* file
_defaults:
# automatically injects dependencies in your services
autowire: false
# automatically registers your services as commands, event subscribers, etc.
autoconfigure: false
# this means you cannot fetch services directly from the container via $container->get()
# if you need to do this, you can override this setting on individual services
public: false

audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- method: 'addPersister'
argument:
- '@audit.persister_elasticsearch'


The compiled cach class looks like:



$this->services['audit.persister.base'] = $instance = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister();

$instance->addPersister();


An i got the error:



 Type error: Too few arguments to function MyBundleSecurityAuditPersisterChainedEntityTrailPersister::addPersister(), 0 passed in /var/www/html/api/var/cache/local/ContainerAdjsiif/getAudit_Persister_BaseService.php on line 14 and exactly 1 expected


The error is correct. Because the cached class creator does not provide the argument that i have set in config.



Anyone an idea why the argument will not set in generated cache?










share|improve this question























  • Hint: Cache is cleared.

    – RalfGe
    Nov 22 '18 at 9:22














0












0








0








i use Symfony 3.4 and i try to migrate an Silex Application to it. So i cant use the autowiring of Symfony.



My service.yml looks like



services:
# default configuration for services in *this* file
_defaults:
# automatically injects dependencies in your services
autowire: false
# automatically registers your services as commands, event subscribers, etc.
autoconfigure: false
# this means you cannot fetch services directly from the container via $container->get()
# if you need to do this, you can override this setting on individual services
public: false

audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- method: 'addPersister'
argument:
- '@audit.persister_elasticsearch'


The compiled cach class looks like:



$this->services['audit.persister.base'] = $instance = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister();

$instance->addPersister();


An i got the error:



 Type error: Too few arguments to function MyBundleSecurityAuditPersisterChainedEntityTrailPersister::addPersister(), 0 passed in /var/www/html/api/var/cache/local/ContainerAdjsiif/getAudit_Persister_BaseService.php on line 14 and exactly 1 expected


The error is correct. Because the cached class creator does not provide the argument that i have set in config.



Anyone an idea why the argument will not set in generated cache?










share|improve this question














i use Symfony 3.4 and i try to migrate an Silex Application to it. So i cant use the autowiring of Symfony.



My service.yml looks like



services:
# default configuration for services in *this* file
_defaults:
# automatically injects dependencies in your services
autowire: false
# automatically registers your services as commands, event subscribers, etc.
autoconfigure: false
# this means you cannot fetch services directly from the container via $container->get()
# if you need to do this, you can override this setting on individual services
public: false

audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- method: 'addPersister'
argument:
- '@audit.persister_elasticsearch'


The compiled cach class looks like:



$this->services['audit.persister.base'] = $instance = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister();

$instance->addPersister();


An i got the error:



 Type error: Too few arguments to function MyBundleSecurityAuditPersisterChainedEntityTrailPersister::addPersister(), 0 passed in /var/www/html/api/var/cache/local/ContainerAdjsiif/getAudit_Persister_BaseService.php on line 14 and exactly 1 expected


The error is correct. Because the cached class creator does not provide the argument that i have set in config.



Anyone an idea why the argument will not set in generated cache?







symfony service yaml symfony3.4






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 9:14









RalfGeRalfGe

63




63













  • Hint: Cache is cleared.

    – RalfGe
    Nov 22 '18 at 9:22



















  • Hint: Cache is cleared.

    – RalfGe
    Nov 22 '18 at 9:22

















Hint: Cache is cleared.

– RalfGe
Nov 22 '18 at 9:22





Hint: Cache is cleared.

– RalfGe
Nov 22 '18 at 9:22












2 Answers
2






active

oldest

votes


















0














From the documentation, you may have:



  audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- method: 'addPersister'
arguments:
- '@audit.persister_elasticsearch'


arguments with a s at the end.






share|improve this answer


























  • Thx this helps but now i have in a service that need this service the same: $a = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister(); $a->addPersister(); Why isn't it taken into account there?

    – RalfGe
    Nov 22 '18 at 9:45













  • I don't understand. If you want to se this service in aother, you have to add de dependency in the other service's constructor

    – G1.3
    Nov 22 '18 at 9:55











  • yes this is done in service.yml like orm.event_manager.base: factory: 'MyBundleORMFactoryORMEventManagerProto:createBase' class: DoctrineCommonEventManager arguments: - '@orm.audit.handler' - '@orm.audit.changeset_normalizer' - '@validation_manager' - '@annotations.reader' - '@acl_manager' - '@property_accessor' - '@services.propertyExpansion' - '@DoctrineCommonCacheChainCache' - '@audit.persister.base'

    – RalfGe
    Nov 22 '18 at 10:06













  • sorry, i dont know how to formt it

    – RalfGe
    Nov 22 '18 at 10:09











  • I inject now in the factory the service container and getting it directly from there.... This works but it seams that it not work with factory combination.

    – RalfGe
    Nov 22 '18 at 10:23



















1














In Symfony it's convention to write calls in one line:



services:
audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- ['addPersister', ['@audit.persister_elasticsearch']]


Also, you can use PHPStorm with Symfony plugin for autocomplete. Thanks to that, you're saved from typos and it basically writes for you :)






share|improve this answer
























  • Hi, thanks for replay. Where do you have this information about the convention. When you take a look in symfony.com/doc/3.4/service_container/calls.html there are documented as i am use.

    – RalfGe
    Nov 26 '18 at 7:48











  • Hi, documentation != convention. I'd look for code on Github in Symfony + bundles: github.com/symfony/symfony/… I use Symfony for 5 years, make bundles, applications above it, but I never saw using "arguments" explicitly in Yaml configs.

    – Tomáš Votruba
    Nov 26 '18 at 8:55








  • 1





    Tanks for your help

    – RalfGe
    Nov 26 '18 at 12:43











  • You're welcome! If you migrate bigger chunks of code (5+ hours of work) from Silex to Symfony, you can use Rector to that (github.com/rectorphp/rector)

    – Tomáš Votruba
    Nov 26 '18 at 12:58






  • 1





    thx again, i will take a look at this tool

    – RalfGe
    Nov 27 '18 at 14:15











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427396%2fsymfony-3-4-dont-set-arguments-when-i-configure-it-in-yaml-service-config%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














From the documentation, you may have:



  audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- method: 'addPersister'
arguments:
- '@audit.persister_elasticsearch'


arguments with a s at the end.






share|improve this answer


























  • Thx this helps but now i have in a service that need this service the same: $a = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister(); $a->addPersister(); Why isn't it taken into account there?

    – RalfGe
    Nov 22 '18 at 9:45













  • I don't understand. If you want to se this service in aother, you have to add de dependency in the other service's constructor

    – G1.3
    Nov 22 '18 at 9:55











  • yes this is done in service.yml like orm.event_manager.base: factory: 'MyBundleORMFactoryORMEventManagerProto:createBase' class: DoctrineCommonEventManager arguments: - '@orm.audit.handler' - '@orm.audit.changeset_normalizer' - '@validation_manager' - '@annotations.reader' - '@acl_manager' - '@property_accessor' - '@services.propertyExpansion' - '@DoctrineCommonCacheChainCache' - '@audit.persister.base'

    – RalfGe
    Nov 22 '18 at 10:06













  • sorry, i dont know how to formt it

    – RalfGe
    Nov 22 '18 at 10:09











  • I inject now in the factory the service container and getting it directly from there.... This works but it seams that it not work with factory combination.

    – RalfGe
    Nov 22 '18 at 10:23
















0














From the documentation, you may have:



  audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- method: 'addPersister'
arguments:
- '@audit.persister_elasticsearch'


arguments with a s at the end.






share|improve this answer


























  • Thx this helps but now i have in a service that need this service the same: $a = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister(); $a->addPersister(); Why isn't it taken into account there?

    – RalfGe
    Nov 22 '18 at 9:45













  • I don't understand. If you want to se this service in aother, you have to add de dependency in the other service's constructor

    – G1.3
    Nov 22 '18 at 9:55











  • yes this is done in service.yml like orm.event_manager.base: factory: 'MyBundleORMFactoryORMEventManagerProto:createBase' class: DoctrineCommonEventManager arguments: - '@orm.audit.handler' - '@orm.audit.changeset_normalizer' - '@validation_manager' - '@annotations.reader' - '@acl_manager' - '@property_accessor' - '@services.propertyExpansion' - '@DoctrineCommonCacheChainCache' - '@audit.persister.base'

    – RalfGe
    Nov 22 '18 at 10:06













  • sorry, i dont know how to formt it

    – RalfGe
    Nov 22 '18 at 10:09











  • I inject now in the factory the service container and getting it directly from there.... This works but it seams that it not work with factory combination.

    – RalfGe
    Nov 22 '18 at 10:23














0












0








0







From the documentation, you may have:



  audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- method: 'addPersister'
arguments:
- '@audit.persister_elasticsearch'


arguments with a s at the end.






share|improve this answer















From the documentation, you may have:



  audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- method: 'addPersister'
arguments:
- '@audit.persister_elasticsearch'


arguments with a s at the end.







share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 23 '18 at 11:13

























answered Nov 22 '18 at 9:26









G1.3G1.3

968111




968111













  • Thx this helps but now i have in a service that need this service the same: $a = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister(); $a->addPersister(); Why isn't it taken into account there?

    – RalfGe
    Nov 22 '18 at 9:45













  • I don't understand. If you want to se this service in aother, you have to add de dependency in the other service's constructor

    – G1.3
    Nov 22 '18 at 9:55











  • yes this is done in service.yml like orm.event_manager.base: factory: 'MyBundleORMFactoryORMEventManagerProto:createBase' class: DoctrineCommonEventManager arguments: - '@orm.audit.handler' - '@orm.audit.changeset_normalizer' - '@validation_manager' - '@annotations.reader' - '@acl_manager' - '@property_accessor' - '@services.propertyExpansion' - '@DoctrineCommonCacheChainCache' - '@audit.persister.base'

    – RalfGe
    Nov 22 '18 at 10:06













  • sorry, i dont know how to formt it

    – RalfGe
    Nov 22 '18 at 10:09











  • I inject now in the factory the service container and getting it directly from there.... This works but it seams that it not work with factory combination.

    – RalfGe
    Nov 22 '18 at 10:23



















  • Thx this helps but now i have in a service that need this service the same: $a = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister(); $a->addPersister(); Why isn't it taken into account there?

    – RalfGe
    Nov 22 '18 at 9:45













  • I don't understand. If you want to se this service in aother, you have to add de dependency in the other service's constructor

    – G1.3
    Nov 22 '18 at 9:55











  • yes this is done in service.yml like orm.event_manager.base: factory: 'MyBundleORMFactoryORMEventManagerProto:createBase' class: DoctrineCommonEventManager arguments: - '@orm.audit.handler' - '@orm.audit.changeset_normalizer' - '@validation_manager' - '@annotations.reader' - '@acl_manager' - '@property_accessor' - '@services.propertyExpansion' - '@DoctrineCommonCacheChainCache' - '@audit.persister.base'

    – RalfGe
    Nov 22 '18 at 10:06













  • sorry, i dont know how to formt it

    – RalfGe
    Nov 22 '18 at 10:09











  • I inject now in the factory the service container and getting it directly from there.... This works but it seams that it not work with factory combination.

    – RalfGe
    Nov 22 '18 at 10:23

















Thx this helps but now i have in a service that need this service the same: $a = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister(); $a->addPersister(); Why isn't it taken into account there?

– RalfGe
Nov 22 '18 at 9:45







Thx this helps but now i have in a service that need this service the same: $a = new MyBundleSecurityAuditPersisterChainedEntityTrailPersister(); $a->addPersister(); Why isn't it taken into account there?

– RalfGe
Nov 22 '18 at 9:45















I don't understand. If you want to se this service in aother, you have to add de dependency in the other service's constructor

– G1.3
Nov 22 '18 at 9:55





I don't understand. If you want to se this service in aother, you have to add de dependency in the other service's constructor

– G1.3
Nov 22 '18 at 9:55













yes this is done in service.yml like orm.event_manager.base: factory: 'MyBundleORMFactoryORMEventManagerProto:createBase' class: DoctrineCommonEventManager arguments: - '@orm.audit.handler' - '@orm.audit.changeset_normalizer' - '@validation_manager' - '@annotations.reader' - '@acl_manager' - '@property_accessor' - '@services.propertyExpansion' - '@DoctrineCommonCacheChainCache' - '@audit.persister.base'

– RalfGe
Nov 22 '18 at 10:06







yes this is done in service.yml like orm.event_manager.base: factory: 'MyBundleORMFactoryORMEventManagerProto:createBase' class: DoctrineCommonEventManager arguments: - '@orm.audit.handler' - '@orm.audit.changeset_normalizer' - '@validation_manager' - '@annotations.reader' - '@acl_manager' - '@property_accessor' - '@services.propertyExpansion' - '@DoctrineCommonCacheChainCache' - '@audit.persister.base'

– RalfGe
Nov 22 '18 at 10:06















sorry, i dont know how to formt it

– RalfGe
Nov 22 '18 at 10:09





sorry, i dont know how to formt it

– RalfGe
Nov 22 '18 at 10:09













I inject now in the factory the service container and getting it directly from there.... This works but it seams that it not work with factory combination.

– RalfGe
Nov 22 '18 at 10:23





I inject now in the factory the service container and getting it directly from there.... This works but it seams that it not work with factory combination.

– RalfGe
Nov 22 '18 at 10:23













1














In Symfony it's convention to write calls in one line:



services:
audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- ['addPersister', ['@audit.persister_elasticsearch']]


Also, you can use PHPStorm with Symfony plugin for autocomplete. Thanks to that, you're saved from typos and it basically writes for you :)






share|improve this answer
























  • Hi, thanks for replay. Where do you have this information about the convention. When you take a look in symfony.com/doc/3.4/service_container/calls.html there are documented as i am use.

    – RalfGe
    Nov 26 '18 at 7:48











  • Hi, documentation != convention. I'd look for code on Github in Symfony + bundles: github.com/symfony/symfony/… I use Symfony for 5 years, make bundles, applications above it, but I never saw using "arguments" explicitly in Yaml configs.

    – Tomáš Votruba
    Nov 26 '18 at 8:55








  • 1





    Tanks for your help

    – RalfGe
    Nov 26 '18 at 12:43











  • You're welcome! If you migrate bigger chunks of code (5+ hours of work) from Silex to Symfony, you can use Rector to that (github.com/rectorphp/rector)

    – Tomáš Votruba
    Nov 26 '18 at 12:58






  • 1





    thx again, i will take a look at this tool

    – RalfGe
    Nov 27 '18 at 14:15
















1














In Symfony it's convention to write calls in one line:



services:
audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- ['addPersister', ['@audit.persister_elasticsearch']]


Also, you can use PHPStorm with Symfony plugin for autocomplete. Thanks to that, you're saved from typos and it basically writes for you :)






share|improve this answer
























  • Hi, thanks for replay. Where do you have this information about the convention. When you take a look in symfony.com/doc/3.4/service_container/calls.html there are documented as i am use.

    – RalfGe
    Nov 26 '18 at 7:48











  • Hi, documentation != convention. I'd look for code on Github in Symfony + bundles: github.com/symfony/symfony/… I use Symfony for 5 years, make bundles, applications above it, but I never saw using "arguments" explicitly in Yaml configs.

    – Tomáš Votruba
    Nov 26 '18 at 8:55








  • 1





    Tanks for your help

    – RalfGe
    Nov 26 '18 at 12:43











  • You're welcome! If you migrate bigger chunks of code (5+ hours of work) from Silex to Symfony, you can use Rector to that (github.com/rectorphp/rector)

    – Tomáš Votruba
    Nov 26 '18 at 12:58






  • 1





    thx again, i will take a look at this tool

    – RalfGe
    Nov 27 '18 at 14:15














1












1








1







In Symfony it's convention to write calls in one line:



services:
audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- ['addPersister', ['@audit.persister_elasticsearch']]


Also, you can use PHPStorm with Symfony plugin for autocomplete. Thanks to that, you're saved from typos and it basically writes for you :)






share|improve this answer













In Symfony it's convention to write calls in one line:



services:
audit.persister.base:
class: MyBundleSecurityAuditPersisterChainedEntityTrailPersister
calls:
- ['addPersister', ['@audit.persister_elasticsearch']]


Also, you can use PHPStorm with Symfony plugin for autocomplete. Thanks to that, you're saved from typos and it basically writes for you :)







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 23 '18 at 14:39









Tomáš VotrubaTomáš Votruba

9,40053861




9,40053861













  • Hi, thanks for replay. Where do you have this information about the convention. When you take a look in symfony.com/doc/3.4/service_container/calls.html there are documented as i am use.

    – RalfGe
    Nov 26 '18 at 7:48











  • Hi, documentation != convention. I'd look for code on Github in Symfony + bundles: github.com/symfony/symfony/… I use Symfony for 5 years, make bundles, applications above it, but I never saw using "arguments" explicitly in Yaml configs.

    – Tomáš Votruba
    Nov 26 '18 at 8:55








  • 1





    Tanks for your help

    – RalfGe
    Nov 26 '18 at 12:43











  • You're welcome! If you migrate bigger chunks of code (5+ hours of work) from Silex to Symfony, you can use Rector to that (github.com/rectorphp/rector)

    – Tomáš Votruba
    Nov 26 '18 at 12:58






  • 1





    thx again, i will take a look at this tool

    – RalfGe
    Nov 27 '18 at 14:15



















  • Hi, thanks for replay. Where do you have this information about the convention. When you take a look in symfony.com/doc/3.4/service_container/calls.html there are documented as i am use.

    – RalfGe
    Nov 26 '18 at 7:48











  • Hi, documentation != convention. I'd look for code on Github in Symfony + bundles: github.com/symfony/symfony/… I use Symfony for 5 years, make bundles, applications above it, but I never saw using "arguments" explicitly in Yaml configs.

    – Tomáš Votruba
    Nov 26 '18 at 8:55








  • 1





    Tanks for your help

    – RalfGe
    Nov 26 '18 at 12:43











  • You're welcome! If you migrate bigger chunks of code (5+ hours of work) from Silex to Symfony, you can use Rector to that (github.com/rectorphp/rector)

    – Tomáš Votruba
    Nov 26 '18 at 12:58






  • 1





    thx again, i will take a look at this tool

    – RalfGe
    Nov 27 '18 at 14:15

















Hi, thanks for replay. Where do you have this information about the convention. When you take a look in symfony.com/doc/3.4/service_container/calls.html there are documented as i am use.

– RalfGe
Nov 26 '18 at 7:48





Hi, thanks for replay. Where do you have this information about the convention. When you take a look in symfony.com/doc/3.4/service_container/calls.html there are documented as i am use.

– RalfGe
Nov 26 '18 at 7:48













Hi, documentation != convention. I'd look for code on Github in Symfony + bundles: github.com/symfony/symfony/… I use Symfony for 5 years, make bundles, applications above it, but I never saw using "arguments" explicitly in Yaml configs.

– Tomáš Votruba
Nov 26 '18 at 8:55







Hi, documentation != convention. I'd look for code on Github in Symfony + bundles: github.com/symfony/symfony/… I use Symfony for 5 years, make bundles, applications above it, but I never saw using "arguments" explicitly in Yaml configs.

– Tomáš Votruba
Nov 26 '18 at 8:55






1




1





Tanks for your help

– RalfGe
Nov 26 '18 at 12:43





Tanks for your help

– RalfGe
Nov 26 '18 at 12:43













You're welcome! If you migrate bigger chunks of code (5+ hours of work) from Silex to Symfony, you can use Rector to that (github.com/rectorphp/rector)

– Tomáš Votruba
Nov 26 '18 at 12:58





You're welcome! If you migrate bigger chunks of code (5+ hours of work) from Silex to Symfony, you can use Rector to that (github.com/rectorphp/rector)

– Tomáš Votruba
Nov 26 '18 at 12:58




1




1





thx again, i will take a look at this tool

– RalfGe
Nov 27 '18 at 14:15





thx again, i will take a look at this tool

– RalfGe
Nov 27 '18 at 14:15


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427396%2fsymfony-3-4-dont-set-arguments-when-i-configure-it-in-yaml-service-config%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

MongoDB - Not Authorized To Execute Command

How to fix TextFormField cause rebuild widget in Flutter

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith