openbmc/bmcweb/DEVELOPING.md

132 bmcweb's Redfish implementation, including Redfish OEM Resources, shall conform
133 to the Redfish specification. Please keep bmcweb's
134 [Redfish support document](https://github.com/openbmc/bmcweb/blob/master/docs/Redfish.md)
136 [OEM SCHEMAS](https://github.com/openbmc/bmcweb/blob/master/docs/OEM_SCHEMAS.md).
143 [Common Errors](https://github.com/openbmc/bmcweb/blob/master/docs/COMMON_ERRORS.md).
153 - Why are the changes useful? Given that bmcweb is a user-facing daemon, commits
175 To that end, bmcweb will do its' best to insulate clients from breaking api
180 configurable would increase the software complexity, therefore bmcweb makes
188 Special note: Code exists in bmcweb that is missing upstream backends to make it
204 .clang-tidy file in the root of bmcweb, and are expected to be passing.
210 Five bmcweb logging levels are supported, from least to most severity:
221   traffic. "critical" should be used when bmcweb encountered an event or entered
222   a state that caused crucial function to stop working or when bmcweb
226   conditions that prevented bmcweb from fulfilling the request. "error" shall be
237 bmcweb by default is compiled with runtime logging disabled, as a performance
248 EXTRA_OEMESON:pn-bmcweb:append = "-Dbmcweb-logging='debug'"
251 bmcweb also supports setting logging level at runtime. The bmcweb CLI
256 bmcweb loglevel info