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
Unless I'm missing a configuration, it seems as if conf errors out when it hits the first error in parsing. For example, the first required field it processes that does not have a value provided by the host causes it to immediately error out. There could be other parsing errors that come afterward that are not presented to the caller that can only be discovered by fixing the first failure, re-running, fixing the next failure, re-running, rinse and repeat.
It would be helpful (and more efficient!) to collect all non-fatal errors during parsing and then present them to the caller at the end of parsing. Doing so would enable the caller to fix all errors at once instead of one at a time.
The text was updated successfully, but these errors were encountered:
Unless I'm missing a configuration, it seems as if
conf
errors out when it hits the first error in parsing. For example, the firstrequired
field it processes that does not have a value provided by the host causes it to immediately error out. There could be other parsing errors that come afterward that are not presented to the caller that can only be discovered by fixing the first failure, re-running, fixing the next failure, re-running, rinse and repeat.It would be helpful (and more efficient!) to collect all non-fatal errors during parsing and then present them to the caller at the end of parsing. Doing so would enable the caller to fix all errors at once instead of one at a time.
The text was updated successfully, but these errors were encountered: