summaryrefslogtreecommitdiff
path: root/src/reference_tree.ml
AgeCommit message (Collapse)Author
2026-04-16T8488: add utility refpath_from_partialJohn Estabrook
Infer the reference path from a path that may or may not contain intervening tag nodes. Return an empty list on a nonsensical path.
2026-03-11T8269: handle element constraintSilenceOutput in creation of ref treeJohn Estabrook
2026-02-06T8232: add util get_subtree for reference_treeJohn Estabrook
This is the direct analogue of Config_tree.get_subtree, a safe wrapper around Vytree.get. Note that the twin functions could easily have been abstracted under Tree_alg, however, for such simple functions the redundancy is preferable.
2026-02-06T8232: simplify return value of fold_tree_with_pathJohn Estabrook
The details do not need to be exposed in the function signature.
2025-12-17T8061: add function get_completion_envJohn Estabrook
2025-12-17T8061: add function get_default_valueJohn Estabrook
2025-12-17T8061: simplify allowed_edit_node with path_typeJohn Estabrook
2025-12-17T8061: extend node_type to path_type for path characteristicsJohn Estabrook
For an arbitrary path, determine if it has the characterists of a configuration path, and return the potential node type, solely in terms of the reference tree. No validation is taking place on values.
2025-12-17T8061: add boolean test for compatibility of path with reference treeJohn Estabrook
2025-12-17T8061: require strict check of existence in refpathJohn Estabrook
For use in reference_path_exists, add strict check in the utility that forms the reference path from a config path.
2025-12-17T8061: add test potential_leaf_value and refine error messagesJohn Estabrook
2025-12-17T8009: fix logic in test potential_tag_valueJohn Estabrook
2025-11-24T8009: add allowed_edit_level to test necessary conditions on pathJohn Estabrook
2025-11-20T8009: remove unnecessary alert on empty path for refpathJohn Estabrook
2025-11-11T7988: move function flag to util.ml for general useJohn Estabrook
2025-11-03T7915: add compiler alerts and annotationsJohn Estabrook
2025-08-13T7718: add revised validate_tree methodJohn Estabrook
2025-05-13deps: T7450: use PCRE2 instead of the original, outdated PCREDaniil Baturin
2025-04-11T7321: fix bug in split_path which missed tag valuesJohn Estabrook
2025-04-02T7292: add utility functions to set tag/leaf data on newly defined pathJohn Estabrook
The vyconfd set operation requires configuration of tag and leaf fields from reference_tree data.
2025-01-30T6946: add utilities for commit algorithmJohn Estabrook
2025-01-13T6342: formating and delete trailing whitespacerebortg
2025-01-08T6342: add parsing of docs elementrebortg
2024-10-24T6718: format error outputJohn Estabrook
2024-10-24T6718: validate_path returns unit instead of (path, value)John Estabrook
Splitting of path arg into (path, value), as originally returned by validate_path, is now handled by a utility function. validate_path returns unit on success and raises error with output on failure.
2024-10-24T6718: update value_checker to return validator output on errorJohn Estabrook
2024-10-24T6718: add function refpath: config path -> reference_tree pathJohn Estabrook
2024-10-24T6718: add functor for internal repJohn Estabrook
2024-10-24T6718: minor changes to support vyconf testsJohn Estabrook
2024-10-24T6718: move validate_path from vyconfJohn Estabrook
2024-05-26T6404: add constraintGroup element to reference treeJohn Estabrook
2024-03-21T6149: update node_data if necessary when merging nodesJohn Estabrook
2023-07-20T5385: catch correct errors in Xml_light Xml.parse_fileJohn Estabrook
2023-05-10T5194: drop keep_order fieldJohn Estabrook
This is not applicable under the current node sorting; drop for now.
2023-05-10T5194: ignore syntaxVersion elementsJohn Estabrook
syntaxVersion elements are post-processed in the Python reference dict
2023-05-10T5194: override json serialization for node_type variantJohn Estabrook
2023-05-10T5194: add default_valueJohn Estabrook
2023-05-10T5194: add completion_helpJohn Estabrook
2023-05-10T5194: allow for empty element string and child order in valueHelpJohn Estabrook
One needs to handle the pathological cases of an empty element string and arbitrary order of child elements. Neither are prohibited, and the former has a use case (for now).
2023-05-10T5194: add render_jsonJohn Estabrook
2023-05-10T5194: insert_maybe as node names exist in multiple interface-def filesJohn Estabrook
2023-05-10T5194: add priority elementJohn Estabrook
2023-05-10T5194: use empty string as name of root to avoid conflictJohn Estabrook
cf. 4df07f8e for details
2023-05-10T5194: remove unused variables and flagJohn Estabrook
2023-05-10T5194: add util functions for reference treeJohn Estabrook
2023-05-10T5194: import reference_tree from vyconfJohn Estabrook