James E. Blair 84e0e76e2f Add error information to config-errors API endpoint ... This is the first in a series of changes to improve the usability of the web view of config errors. The end goal is to be able to display them in a more structured manner. A secondary goal is to eventually add warnings (eg, deprecation warnings) which is really only feasible if we have structured presentation of errors. This change does the following: * Adds severity and error names to existing configuration errors * And makes them available via the config-errors API endpoint * Reduces the call sites for the error accumulator (LoadingErrors.addError) * Unifies the calling convention for the accumulator (we stop passing in Exception objects) Change-Id: Ia17dd3e7ad8cdfa8a07bb03b871078415d0c145e		2023-05-25 15:41:37 -07:00
..
__init__.py	Add error information to config-errors API endpoint	2023-05-25 15:41:37 -07:00
handler.py	Replace use of aiohttp with cherrypy	2018-05-31 09:09:26 -07:00
logutil.py	Identify cherrypy requests in logs	2022-02-02 16:16:27 -08:00