parser data REFACTOR split NETCONF notification and reply parsing
Because there is never a situation when either of
these messages could be parsed directly, the transport
protocol metadata must first be handled. Also, the
old API did not allow for direct notification
parsing, always only both a reply and notification.
diff --git a/src/parser_json.c b/src/parser_json.c
index bccd286..37b7e68 100644
--- a/src/parser_json.c
+++ b/src/parser_json.c
@@ -1383,16 +1383,16 @@
assert(status == LYJSON_OBJECT);
switch (data_type) {
- case LYD_TYPE_YANG_DATA:
+ case LYD_TYPE_DATA_YANG:
int_opts = LYD_INTOPT_WITH_SIBLINGS;
break;
- case LYD_TYPE_YANG_RPC:
+ case LYD_TYPE_RPC_YANG:
int_opts = LYD_INTOPT_RPC | LYD_INTOPT_ACTION | LYD_INTOPT_NO_SIBLINGS;
break;
- case LYD_TYPE_YANG_NOTIF:
+ case LYD_TYPE_NOTIF_YANG:
int_opts = LYD_INTOPT_NOTIF | LYD_INTOPT_NO_SIBLINGS;
break;
- case LYD_TYPE_YANG_REPLY:
+ case LYD_TYPE_REPLY_YANG:
int_opts = LYD_INTOPT_REPLY | LYD_INTOPT_NO_SIBLINGS;
break;
default: