Skip to content
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

Missing ability to provide scope ID to config fixture service #17

Open
Vinai opened this issue May 21, 2013 · 0 comments
Open

Missing ability to provide scope ID to config fixture service #17

Vinai opened this issue May 21, 2013 · 0 comments

Comments

@Vinai
Copy link
Contributor

Vinai commented May 21, 2013

The config fixture step provides the ability to specify a config scope (that is "default", "website" or "store"). For example:

When I set config value for "some/config/path" to "1" in "store" scope

The problem is, to be usable with anything but "default", a scope identifier needs to be specified, for example as follows:

When I set config value for "some/config/path" to "1" in "store" "usa" scope

In the table core_config_data the scope ID is stored as an integer ID, using 0 for the "default" scope.
To make this more reusable the scope ID should be specifiable as a website or store view code.

References:

MageTest\MagentoExtension\Context\MagentoContext::iSetConfigValueForScope($path, $value, $scope)
MageTest\MagentoExtension\Service\ConfigManager::setCoreConfig($path, $value, $scope)
MageTest\MagentoExtension\Service\Config\CoreConfig::set($path, $value, $scope)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants