John Snow <js...@redhat.com> writes: > Although "deprecated" is a feature (and *will* appear in the features > list), add a special :deprecated: option to generate an eye-catch that > makes this information very hard to miss. > > (The intent is to modify qapidoc.py to add this option whenever it > detects that the features list attached to a definition contains the > "deprecated" entry.) > > - > > RFC: Technically, this object-level option is un-needed and could be > replaced with a standard content-level directive that e.g. qapidoc.py > could insert at the beginning of the content block. I've done it here as > an option to demonstrate how it would be possible to do. > > It's a matter of taste for "where" we feel like implementing it. > > One benefit of doing it this way is that we can create a single > containing box to set CSS style options controlling the flow of multiple > infoboxes. The other way to achieve that would be to create a directive > that allows us to set multiple options instead, e.g.: > > .. qapi:infoboxes:: deprecated unstable > > or possibly: > > .. qapi:infoboxes:: > :deprecated: > :unstable: > > For now, I've left these as top-level QAPI object options. "Hey, it works."
I think we agreed to delete the text from RFC: until here. > P.S., I outsourced the CSS ;) > > Signed-off-by: Harmonie Snow <harmo...@gmail.com> > Signed-off-by: John Snow <js...@redhat.com>
