| Age | Commit message (Collapse) | Author |
|---|
|
Change-Id: I61efeb666ff7481c05fcb247168290e86a250151
|
|
|
|
Fix #8162
The test is changed to compare `nlohmann::json` values, not strings of dumped
JSON, which allows us to format things more nicely.
|
|
Use it everywhere it could be also.
|
|
They are put in the manual separate pages under the new overarching
description of experimental features.
The settings page just lists the valid experimental feature names (so
people know what a valid setting entry looks like), with links to those
pages. It doesn't attempt to describe each experimental feature as that
is too much information for the configuration settings section.
|
|
Instead of constructing a markdown list in C++ (which involved all sorts
of nasty string literals), export some JSON and assemble it with the
manual build system.
Besides following the precedent set with other dumped data, this is a
better separate of content and presentation; if we decide for example we
want to display this information in a different way, or in a different
section of the manual, it will become much easier to do so.
|
|
|
|
|
|
Since setting names are not unique we don't have an easy way to
produce unique anchors.
|
|
|
|
|
|
it was quite a pain to manipulate strings just with `builtins`
|
|
|
|
|
