-
Notifications
You must be signed in to change notification settings - Fork 33
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
Allow for selectively INCLUDING config types instead of EXCLUDING via config/plugins.ts
#96
Comments
Hi @EsGeh, Thanks for reporting this issue. I would suggest going with solution nr 2. If a specific config is for some reason excluded and included through the different config options, then the exclude options should have priority. So a config that is included and excluded will not be synced with the plugin. Also this new |
Feature request
Summary
Quick summary what's this feature request about.
Allow for selectively including config types via
config/plugins.ts
.Why is it needed?
I'd like to be able to only include only very few very specific types to be synchronized, e.g.
core-store.plugin_content_manager_configuration_content_types::api::...
.With the current config format this is almost impossible, because there is no way to specify what to include, but only what to exclude from the defaults. So in order to include very specific config types, one would have to list "everything else" in the
excludedConfig
field of the config, which is unpractical, and in many cases impossible.Suggested solution(s)
Conservative solution:
Consider entries in
customTypes
even if they match some pattern listed inexcludedConfig
. This way you may exclude "everything" by listing all default types inexcludedConfig
and then explicitly list what you'd like toinclude
viacustomTypes
.More flexible solution
includedConfig
is consideredRelated issue(s)/PR(s)
Unknown.
The text was updated successfully, but these errors were encountered: