Michal Vasko

It turns out that `ietf-yang-library` is using `\d` as `[0-9]`, which it seems is wrong but based on that I decided to change the warning into a verbose message.

Too late to change anything about that, anyway, the best we could hope for is an errata. Before you mentioned it, I, for some reason, assumed that `\d` works the...

Yes, ideally. In practice it would lead to most people turning off warnings altogether (making things worse) and us getting spammed by others asking about the warning and how to...

Only now have I found out that PCRE2 has a flag for Unicode support of `\d`, `\w` and so on, so I have just used it.

*libyang* 2.0.7 is more than a year old when version 2 had just been shortly available publicly, so there were many problems. You will have to update it to fix...

Okay, it should be fixed and this is then a duplicate of #1896.

[Section 9.10.2](https://datatracker.ietf.org/doc/html/rfc7950#section-9.10.2), the last paragraph.

The reason for this is that YANG instance data (`struct lyd_node *`) are always in schema order before any opaque nodes (`struct lyd_node_opaq *`), which have no definition in any...

The advantage is that if you receive, let's say, the reply to a `get` RPC, you have the full running and state data parsed into their corresponding YANG schema nodes...

I understand all that but, strictly speaking, you are relying on the fact that the order of all the nested elements will be kept, which is not guaranteed anywhere. Also,...