Manuel Muth

@christophfroehlich I added a overview to the docs. There the key-value storage is described in a generic example. We could explain the other xml tags there as well. Release notes...

Think i changed everything. @destogl 1. Please check if the deprecation is now how you mentioned it. 2. Please look at the custom export again int the test if this...

> > @saikishor I didn't use unordered_map everywhere as for the name to interface description we want to keep the order in my understanding. O(log(n)) overhead should be ok in...

Now unorderd_map is used everywhere and tests are adjusted accordingly. Further new export_command/state_interface_2() function has been introduced which the user can override to export custom unlisted interfaces. This function is...

> I like the approach, considering the cleaner code as demonstrated with example_1 and the (as by now, theoretical) support of other datatypes. I don't comment on the code as...

@saikishor 1. I think this should be fine for us as i understand std::variant works as typesafe union and is not allowed to allocate additional (dynamic) memory. As we set...

> A short note in the release notes would be great 😇 done

> Can this be closed? Or massively refactored? I Will refactor as soon as other stuff is merged. There are a lot of duplicate changes since i based on first...

its probably not in the package.xml have to check the generation scripts

Maybe we could beside the print_and_exit function add functions like: print_warning print_info .... Which print the given message in a defined way (e.g color coded). This way we would have...