Skip to main content

server_info_body

Function server_info_body 

Source
pub fn server_info_body(config: &ServerConfig) -> Value
Expand description

The response body. The master-key gate is applied by the dispatcher, not here.

The key set and nesting are transcribed from FeaturesRouter and are wire contract. The values are not transcribed: upstream hardcodes almost all of them to true because upstream implements them, and repeating that here would advertise hooks, a global config, cloud jobs, a log API and push, none of which have routes. Parse Dashboard renders its UI from this object, so a copied true becomes a control that 404s when a user clicks it. See FeatureSupport for the reasoning; each flag flips as its subsystem lands.