-
Notifications
You must be signed in to change notification settings - Fork 60
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
Feature/issue 64 include scope #66
base: main
Are you sure you want to change the base?
Feature/issue 64 include scope #66
Conversation
Command/ExportCommand.php
Outdated
"Scope name, multiple values can be comma separated; exports only those scopes.\n". | ||
"\t\tTo export only specific scopes add there ID(s) using a colon and separate them with semicolon.\n". | ||
"\t\tMake sure to use quotes when specifying multiple scope IDs:\n". | ||
"\t\te.g. --includeScope=\"websites:2;3,stores:2;3;4;5\" will export the settings for website IDs 2 and 3 and for the\n". |
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 noticed only afterwards, that separating scope IDs will break the command line. But I could not think of any better separator
Hi @therouv , I fixed the cs-fixer-issues, but I do not understand what might have caused the Unit-Test failure. What does Best regards, Willi |
@therouv Could you please start the tests to see, if they work now? Thank you! |
Hi guys, this is a super important feature. |
Please make sure these boxes are checked before submitting your PR - thank you!
Issue
This PR fixes issue #64 .
Proposed changes
Just allows to specify scope with ids (and without additional option) like:
--includeScope=websites:2,stores:2,3
...