Another feedback:

• add this new command to the CHANGELOG.md

@diosmosis I renamed the command to config:set and tested it, I notice it does not work for me, the config file is not updated... When adding $config->clear() in d1fc19d in the integration test this issue can be reproduced (ie. the config file was not updated). could you take a look?

@mattab fixed the issue & refactored a bit. you can review and/or merge.

Feedback:

• in help text it says NOTE: 'value' must be JSON encoded, so Section.config_setting_name="value" would work but Section.config_setting_name=value would not. but I found that it is actually working eg. ./console config:set --section=Tracker --key=debug --value=value2
  • should this text be removed?
• One can add array values with ./console config:set 'Section.config_setting_name[]="value to append2"' but how does one reset an array to empty? let's add this to command help text + a test case
• Assigning 0 value does not work, but it was expected to work:

$ ./console config:set --section=Tracker --key=debug --value="0"

  [InvalidArgumentException]                                                                        
  Nothing to assign. Add assignments as arguments or use the --section, --key and --value options.  

n help text it says NOTE: 'value' must be JSON encoded, so Section.config_setting_name="value" would work but Section.config_setting_name=value would not. but I found that it is actually working eg. ./console config:set --section=Tracker --key=debug --value=value2

It only needs to be JSON encoded when using arguments, not options.

One can add array values with ./console config:set 'Section.config_setting_name[]="value to append2"' but how does one reset an array to empty? let's add this to command help text + a test case

./console config:set 'Section.config_setting_name=[]' should do it.

Assigning 0 value does not work, but it was expected to work:

Will look into it.

@mattab FYI, fixed the issue + tweaked the docs + added more tests.

Looks good to me! 👍