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.

Sign up for GitHub

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

Jump to bottom

Validate fetched presets #30968

Open
RahulGautamSingh opened this issue Aug 22, 2024 · 0 comments
Open

Validate fetched presets #30968

RahulGautamSingh opened this issue Aug 22, 2024 · 0 comments
Labels
core:config Related to config capabilities and presets priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)

Comments

@RahulGautamSingh
Copy link
Collaborator

RahulGautamSingh commented Aug 22, 2024 •
edited
Loading

The fetched presets are not being validated before being used. This can cause silent problems and waste time during debugging for minor issues in config. Better to handle this when presets are resolved.

Will need to do separately for repo config and admin config as they are reolved at different stages.

Originally posted by @LeoniePhiline in #30967 (reply in thread)
@RahulGautamSingh RahulGautamSingh added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others core:config Related to config capabilities and presets type:feature Feature (new functionality) labels Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
core:config Related to config capabilities and presets priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RahulGautamSingh