Age | Commit message (Collapse) | Author |
|
commands.
|
|
|
|
sorting set commands.
|
|
|
|
The canonical format for valueless nodes is "foo;".
There are two cases: when it's known from the reference tree that
a node is valueless, we should render it the canonical way.
However, a valueless node is not the same as a normal node with no children,
semantically, so nodes that are note valueless should be rendered as "foo {}".
If the reference tree is not present, resort to rendering all nodes
without values as if they were normal nodes with no children
rather than as if they were valueless.
The parser is unaware of the distinction, so there are no implications for it.
|
|
i.e. if they don't contain whitespace or characters of special significance
to the parser (;[]{}#).
|
|
for human consumption.
The idea of the correct (for subsequent parsing) and familiar for all other purposes rendering:
* When rendering the entire config, do not render the invisible "root" node, only render its children.
* When rendering config at specified path, do not include any nodes that are within the path
(e.g. if path "system login" exists, "show system" request output should start with "login {",
not "system { login { ...").
|
|
* Add stand-alone config_tree renderer
* Add tests for stand-alone config_tree renderer
* Add renderer with reference tree
* Add tests for Config_tree renderer with reftree
* Update config files
* Add refactoring functions and correct tests
|
|
|
|
|
|
|
|
|
|
|
|
|
|
input from the reference tree anyway.
Make value modification functions behaviour multi-value node aware.
|
|
|
|
|