docs/yaml/interface.md

9 An interface YAML may have the following sections:
29 A common problem we have found with D-Bus interfaces is having a consistent way
31 meaning to integers, as a C compiler might do, or to have specific strings
40 What we have done in `sdbus++` is to consider enumerations as a first-class
42 have a C++ enumeration defined for it. At a D-Bus level any property or method
50 An enumeration must have the YAML properties `name` and `values` and may
142 A method must have the YAML property `name` and may optionally have
144 must have a `name`, `type`, and optional `description`. Each return must have a
145 `type` and may optionally have a `name` and `description`. Flags are a list of
182 A property must have the YAML property `name` and `type` and may optionally have
223 A signal must have the YAML property `name` and may optionally have a
245 A path must have the YAML property `name` & `value` and may optionally have a
246 `description` and `segments`. Each `segments` entry must have the YAML property
247 `name` & `value` and may optionally have a `description` & nested `segments`.
268 A common approach is to have a single path which is used as a root of all
292 A singleton host service name must have the YAML property `default` and may
293 optionally have a `description`. `xyz.openbmc_project.ObjectMapper` is one such
307 A multiton host service name must have the YAML property `name` & `value` and
308 may optionally have a `description`.