You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 9, 2024. It is now read-only.
This issue is just to share an idea for a feature for the WebMangler CI: add a subcommand to validate a configuration file (find missing fields that are required; find present fields that are unknown; find fields with invalid values; etc.) and/or add a --strict flag that only runs WebMangler if the configuration file is completely valid.
The text was updated successfully, but these errors were encountered:
In #271 an new field will be added to the WebMangler CLI configuration, named reporters, that should(?) be given one (1) or more reporters. It may make sense to validate that there is at least on reporter provided (if configured).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue is just to share an idea for a feature for the WebMangler CI: add a subcommand to validate a configuration file (find missing fields that are required; find present fields that are unknown; find fields with invalid values; etc.) and/or add a
--strict
flag that only runs WebMangler if the configuration file is completely valid.The text was updated successfully, but these errors were encountered: