Skip to content

Conversation

@wilfriedwolf
Copy link

Please make sure these boxes are checked before submitting your PR - thank you!

  • Pull request is based against main branch
  • README.md reflects changes (if applicable)
  • New files contain a license header (none added)

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

...

"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".
Copy link
Author

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

@wilfriedwolf
Copy link
Author

Hi @therouv ,

I fixed the cs-fixer-issues, but I do not understand what might have caused the Unit-Test failure.

grafik

What does 'module_name' is not set mean? And: How could I pretest?

Best regards,

Willi

@wilfriedwolf
Copy link
Author

@therouv Could you please start the tests to see, if they work now? Thank you!

@itaymesh
Copy link

itaymesh commented Dec 2, 2024

Hi guys, this is a super important feature.
Can you please merge and release it.
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants