Skip to content

Cli config show returns Configuration ... doesn't exist if value is 0 or empty string #28549

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

Merged
merged 6 commits into from
Jul 16, 2020

Conversation

engcom-Charlie
Copy link
Contributor

Description (*)

Fixed and covered by test.

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes ./bin/magento config:show returns "Configuration for path: '...' doesn't exist" if config value equals to 0 or empty string #23290

Manual testing scenarios (*)

  1. Set any config to 0 or '' (empty string)
  2. Check value cli bin/magento config:show {{path}}

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Jun 5, 2020

Hi @engcom-Charlie. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

@engcom-Charlie
Copy link
Contributor Author

@magento run all tests

@aleron75 aleron75 added Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Cleanup labels Jun 6, 2020
aleron75
aleron75 previously approved these changes Jun 6, 2020
@magento-engcom-team
Copy link
Contributor

Hi @aleron75, thank you for the review.
ENGCOM-7629 has been created to process this Pull Request

Copy link
Contributor

@engcom-Alfa engcom-Alfa left a comment

Choose a reason for hiding this comment

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

Hi @engcom-Charlie .

During testing, we faced the issue.

Manual testing scenario:

  1. Run in console command: ./bin/magento config:set analytics/subscription/enabled '' for example;
    ✔️ Value was saved
    Screenshot from 2020-06-09 11-39-56

  2. Run command: ./bin/magento config:show analytics/subscription/enabled

Actual Result: ✖️ Configuration for path doesn't exist..

Screenshot from 2020-06-09 11-40-50

Note: In core_config_data table config was saved with value "NULL"

screenshot_46

@engcom-Charlie Could you take a look?
Thanks!

@ghost ghost dismissed aleron75’s stale review June 9, 2020 08:44

Pull Request state was updated. Re-review required.

@ghost ghost added Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. labels Jun 18, 2020
@magento-engcom-team
Copy link
Contributor

Hi @VladimirZaets, thank you for the review.
ENGCOM-7629 has been created to process this Pull Request

@engcom-Charlie
Copy link
Contributor Author

@magento run all tests

Copy link
Contributor

@aleron75 aleron75 left a comment

Choose a reason for hiding this comment

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

The failing functional test doesn't seem related to this PR; furthermore, I don't understand the code mess checker that complains about too many dependencies which I don't see in the constructor. Thus I approve.

@magento-engcom-team
Copy link
Contributor

Hi @aleron75, thank you for the review.
ENGCOM-7629 has been created to process this Pull Request

@engcom-Charlie
Copy link
Contributor Author

@magento run all tests

@engcom-Charlie
Copy link
Contributor Author

The failing functional test doesn't seem related to this PR; furthermore, I don't understand the code mess checker that complains about too many dependencies which I don't see in the constructor. Thus I approve.

Code mess checker was fallen due to the number of classes in use. So I suppress this warning.
Please approve it.

@engcom-Charlie engcom-Charlie requested a review from aleron75 June 24, 2020 17:54
@magento-engcom-team
Copy link
Contributor

Hi @aleron75, thank you for the review.
ENGCOM-7629 has been created to process this Pull Request

@engcom-Delta
Copy link
Contributor

✔️ QA passed
Before:
#28549MAin

✔️ After:
#28549PR

@engcom-Echo engcom-Echo self-assigned this Jun 26, 2020
@engcom-Echo engcom-Echo added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Jun 26, 2020
@slavvka slavvka added this to the 2.4.1 milestone Jun 26, 2020
@engcom-Delta engcom-Delta added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Jun 30, 2020
magento-engcom-team pushed a commit that referenced this pull request Jul 16, 2020
@magento-engcom-team magento-engcom-team merged commit 60212ab into magento:2.4-develop Jul 16, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jul 16, 2020

Hi @engcom-Charlie, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Cleanup Component: Config Priority: P4 No current plan to fix. Fixing can be deferred as a logical part of more important work. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

./bin/magento config:show returns "Configuration for path: '...' doesn't exist" if config value equals to 0 or empty string
9 participants