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
the high level idea is that some users will find it desirable to have control over how strictly errors within the various configuration files should be treated.
Can we allow/prevent stale reads of cached data if the newly loaded data is bad
option to keep going when one of the set of data files is bad
control whether those settings apply to validation mode and/or the main operation of the server
how do we surface errors that have been suppressed in this cases, and is that itself another option?
This needs some thought before starting to work up the code around it.
The text was updated successfully, but these errors were encountered:
At the lower level, expose an options struct that allows control
over how various checks and conditions are reported out of the
attempt to load the set of shaping files.
Expose a separate list of errors, distinct from warnings.
Each check can either be ignored, a warning, or an error.
Errors cause validate-shaping and --validate mode to exit
with an error condition, whilst warnings are simply emitted
as informational items.
In the shaping helper, it is possible to configure a separate set of
options for the main live service and validation mode, which allows you
to run a more relaxed configuration by default, but be a bit more strict
in your pre-commit and pre-deploy configuration validation pipeline
refs: #287
the high level idea is that some users will find it desirable to have control over how strictly errors within the various configuration files should be treated.
This needs some thought before starting to work up the code around it.
The text was updated successfully, but these errors were encountered: