\hypertarget{doc_decisions_holes_md_autotoc_md1243}{}\doxysection{Problem}\label{doc_decisions_holes_md_autotoc_md1243}
Config files ideally do not copy any structure if they only want to set a single key.\hypertarget{doc_decisions_holes_md_autotoc_md1244}{}\doxysection{Constraints}\label{doc_decisions_holes_md_autotoc_md1244}

\begin{DoxyItemize}
\item strongly hierarchically structured data must still be supported
\end{DoxyItemize}\hypertarget{doc_decisions_holes_md_autotoc_md1245}{}\doxysection{Assumptions}\label{doc_decisions_holes_md_autotoc_md1245}
\hypertarget{doc_decisions_holes_md_autotoc_md1246}{}\doxysection{Considered Alternatives}\label{doc_decisions_holes_md_autotoc_md1246}

\begin{DoxyItemize}
\item data structure is always complete
\item to not allow \char`\"{}directory values\char`\"{} or \char`\"{}directory metadata\char`\"{}
\end{DoxyItemize}\hypertarget{doc_decisions_holes_md_autotoc_md1247}{}\doxysection{Decision}\label{doc_decisions_holes_md_autotoc_md1247}

\begin{DoxyItemize}
\item support holes in Key\+Set
\item See \href{/home/mpranj/workspace/libelektra/src/bindings/cpp/examples/cpp_example_hierarchy.cpp}{\texttt{ hierarchy example}} for how to implement a hierarchy that gets rid of the problem that holes might create when iterating over Key\+Set.
\end{DoxyItemize}\hypertarget{doc_decisions_holes_md_autotoc_md1248}{}\doxysection{Rationale}\label{doc_decisions_holes_md_autotoc_md1248}
\hypertarget{doc_decisions_holes_md_autotoc_md1249}{}\doxysection{Implications}\label{doc_decisions_holes_md_autotoc_md1249}
\hypertarget{doc_decisions_holes_md_autotoc_md1250}{}\doxysection{Related Decisions}\label{doc_decisions_holes_md_autotoc_md1250}
\hypertarget{doc_decisions_holes_md_autotoc_md1251}{}\doxysection{Notes}\label{doc_decisions_holes_md_autotoc_md1251}
