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

[5.x] Prevent certain blueprint config keys getting stripped out #10059

Merged
merged 7 commits into from May 14, 2024

Conversation

jasonvarga
Copy link
Member

@jasonvarga jasonvarga commented May 13, 2024

In #9685 we stripped out redundant blueprint configs where they matched the defaults.

This looks to be a bit heavy handed in some situations.

This PR allows certain keys to be forced into the config even when they match the defaults.

Replaces #10054

before the other PR, the logic was to remove "duplicate" if it was true. this is now saying to always remove it, which is incorrect. partly solves #10040
a force_in_config option will allow configs to avoid getting stripped out. it only applies to fields when used as configs.
it was only being added on the edit route, but should have also been there for the update route.

the reason it didnt show an issue was because all falsey/null values were being stripped out anyway.
@jasonvarga jasonvarga marked this pull request as ready for review May 14, 2024 13:57
@jasonvarga jasonvarga merged commit f00de9a into 5.x May 14, 2024
34 checks passed
@jasonvarga jasonvarga deleted the force-certain-config-keys branch May 14, 2024 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant