Skip to content

fix: match excludedConfig against the config name, not the escaped file name - #241

Open
PaulRichez wants to merge 1 commit into
pluginpal:masterfrom
PaulRichez:fix/excluded-config-names
Open

PaulRichez wants to merge 1 commit into
pluginpal:masterfrom
PaulRichez:fix/excluded-config-names

Conversation

@PaulRichez

Copy link
Copy Markdown

What does it do?

In getAllConfigFromFiles, the excludedConfig check now uses the config name (formattedName, with :: and /), like every other place in the plugin.

Why is it needed?

An exclusion on a name containing : or / only applied to the database side, so the config stayed in the diff as "Only in sync dir". See #240.

How to test it?

Add a content-manager configuration to excludedConfig with the name shown in the admin, e.g. core-store.plugin_content_manager_configuration_content_types::api::article.article, and run config-sync diff: it's no longer listed. (Checked on a Strapi 5.54 app.)

Lint and integration tests pass locally (Node 22).

Note: an exclusion written with the escaped form (##) used to hide the file only; it no longer has an effect. The name to use is the one shown in the admin.

Related issue(s)/PR(s)

Fixes #240

This branch has not been deployed

No deployments
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.

excludedConfig doesn't work for config names containing : or /

1 participant